Maintenance and cleanup operations

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating safe operations with flexible parameters. The description adds valuable behavioral context beyond annotations by specifying what each operation does (e.g., 'Remove expired Files API entries', 'Clean up database inconsistencies') and mentioning the workflows.md patterns. However, it doesn't disclose potential side effects like performance impact or execution time.

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 perfectly structured and concise: a brief introductory sentence followed by a clear bulleted list of operations with specific actions. Every sentence earns its place by providing essential information without redundancy. The front-loaded structure immediately communicates the tool's scope.

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?

Given the tool's moderate complexity (4 parameters, multiple operations) and rich annotations (readOnlyHint, openWorldHint), the description provides good contextual completeness. It explains what each operation does, references external documentation (workflows.md), and covers the tool's scope well. The main gap is the lack of output information (no output schema), but the description compensates reasonably given the annotations.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds meaningful context by explaining what each operation does (e.g., 'Check Files API storage usage vs. ~20GB budget' for check_quota), which helps the agent understand the semantic purpose beyond the parameter definitions. However, it doesn't provide additional parameter-specific guidance beyond what's in the schema.

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 following specific patterns, then enumerates five distinct operations with specific verbs and resources (e.g., 'Remove expired Files API entries', 'Clean old local files'). It distinguishes itself from sibling tools like generate_image or upload_file by focusing on system maintenance rather than content creation or file management.

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?

The description implies usage through the list of available operations (e.g., use check_quota for storage monitoring), but lacks explicit guidance on when to choose this tool over alternatives or prerequisites for use. No when-not-to-use scenarios or comparisons with sibling tools are provided, leaving usage context somewhat implied rather than clearly defined.

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