Maintenance and cleanup operations

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

The annotations declare readOnlyHint=true (suggesting no side effects), but the description lists destructive operations like 'cleanup_expired: Remove expired Files API entries' and 'cleanup_local: Clean old local files', implying data deletion. This is a clear contradiction. Additionally, no disclosure of auth requirements or rate limits.

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 short and uses a bullet list for operations, aiding readability. It is front-loaded with 'Perform maintenance operations'. The reference to 'workflows.md patterns' is vague but does not significantly detract. Every sentence contributes, though the external reference could be clarified.

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?

No output schema is present, and the description does not explain what the tool returns (e.g., a report, status, or nothing). For destructive operations, knowing the output type is important. The dry_run parameter hints at reporting, but the default behavior is unspecified. The tool's impact on data is described, but consequences (e.g., irreversible deletion) are not highlighted.

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 already well-documented. The description adds marginal value by listing operation names with one-line summaries (e.g., 'check_quota: Check Files API storage usage'), which slightly enriches understanding beyond the schema's plain enumeration. However, for dry_run, max_age_hours, and keep_count, no additional semantics are provided.

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 'Perform maintenance operations' and enumerates five specific operations with brief explanations (e.g., 'Remove expired Files API entries'). This distinguishes it from sibling tools (fetch_generation, generate_image, etc.) which are unrelated. The title 'Maintenance and cleanup operations' reinforces the resource.

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 references 'following workflows.md patterns', implying a prescribed usage context, but does not explicitly state when to use this tool versus alternatives (e.g., when to choose cleanup_expired vs. cleanup_local). No when-not-to-use guidance is provided, though sibling tools are unrelated, so confusion is minimal.

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