archive_query

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

No annotations are provided, so the description carries full burden. It hints at mutation ('Archive/Delete') and mentions a paid plan requirement, but lacks details on side effects, reversibility, permissions, or effects on related data.

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?

Very brief (single sentence) and front-loaded with key action, but omits important details. The parenthetical about paid plan could be integrated better.

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?

For a destructive tool with 0% schema coverage and no annotations, the description is insufficient. It does not explain return values, operation idempotency, or what happens to associated data, despite an output schema being present.

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?

Input schema has 0% description coverage, and the description does not explain the 'query_id' parameter. No constraints, format, or context is provided, leaving the agent to infer meaning solely from the parameter name.

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?

Description clearly states the tool archives/deletes a query, with verb 'Archive/Delete' and resource 'query'. It distinguishes from siblings like create_query and execute_query, but could clarify the difference between archiving and deletion.

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?

Only provides a prerequisite ('Requires Paid Plan') but no guidance on when to use this tool versus alternatives, such as update_query or creating a new query. No exclusions or context for when not to use it.

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