Preview report deletion

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by reinforcing 'Nothing is deleted' and revealing the short-lived nature of the token, which is beyond what annotations provide. No contradictions.

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 extremely concise: two sentences with no wasted words. It front-loads the action and includes a clarifying note about non-deletion.

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 one parameter and rich annotations, the description covers the main purpose and behavior. However, it lacks details about the token's lifetime or what happens after token expiry, which could be useful for a preview tool.

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 0%, and the description does not explain the 'reportIds' parameter, its format, or constraints. While the schema includes a pattern, the description should compensate but fails to add meaning.

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 opens Draft or Returned reports for deletion and returns a deletion token. It uses a specific verb ('Open') and resource ('reports'), and distinguishes itself from sibling tools like camcors_delete_reports by explicitly noting 'Nothing is deleted by this tool.'

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 that this tool is a preview step before actual deletion, and it mentions a short-lived deletion token, which hints at a subsequent deletion call. However, it does not explicitly state when not to use it or name alternative tools, so some guidance is missing.

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