Maintenance and cleanup operations

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

The description states the tool performs maintenance operations (including destructive actions like cleanup), but annotations include readOnlyHint=true, creating a contradiction. The tool's mutability is not clarified, and the reference to workflows.md patterns is vague.

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?

The description is concise, with a clear opening sentence and a bullet list of operations. It front-loads the purpose and avoids unnecessary words.

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?

The tool has no output schema, and the description does not explain what the tool returns (e.g., reports, status messages). It also omits details about error handling or sequencing of full_cleanup.

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 the input schema already provides detailed descriptions for all parameters. The description adds the operation list but does not provide additional meaning beyond what the schema offers.

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 states the tool performs maintenance operations and lists specific operations like cleanup_expired, check_quota, etc. It distinguishes itself from siblings (generate_image, show_output_stats, upload_file) by focusing on maintenance tasks.

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?

While the description mentions following workflows.md patterns, it does not explicitly state when to use this tool versus alternatives. The operations are self-explanatory, but there is no guidance on exclusions or conditions for use.

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