Maintenance and cleanup operations

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description states operations like 'cleanup_expired' and 'cleanup_local' that remove data, but annotations declare readOnlyHint=true, a contradiction. No mention of destructive nature beyond operation names. Dry-run parameter is not highlighted. Annotation contradiction flag set to true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is short and well-structured with a bullet list for operations. It is front-loaded with a general statement. No superfluous content, but it could be even more concise by avoiding the external reference.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description should explain what each operation returns or reports. It does not. The contradiction with annotations is not addressed, and the 'workflows.md' reference is unexplained. The tool has multiple operations with different behaviors, but completeness is lacking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds minimal additional meaning—only listing operation names and referencing an external file (workflows.md). The schema already explains each operation, so description adds limited value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's purpose: performing maintenance operations with a list of specific tasks. The sibling tools are unrelated (generate_image, show_output_stats, upload_file), so differentiation is clear. However, the description references 'workflows.md patterns' which may not be accessible, slightly reducing clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives or how to choose between operations. Prerequisites and context are missing. The description merely lists operations without explaining appropriate usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.