delete_shareable_report

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

No annotations are provided, so the description must carry full behavioral disclosure. It states the tool is a utility and revokes a link, but does not explain side effects (e.g., whether the revoke is irreversible), required permissions, or error conditions. The mention of 'hosted endpoint' and 'introspection stub' adds confusion rather than clarity.

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 at two sentences, front-loading the action. However, the last sentence about 'introspection stub' is unnecessary for an agent invoking the tool and could be removed to improve focus.

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 2 optional parameters, no output schema, and allows nested objects. The description omits return value details, error handling, and prerequisite conditions. For a deletion action, critical context like 'is this reversible?' or 'what confirms success?' is missing.

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 coverage is 100% with descriptions, but the descriptions are vague ('Optional high-level request', 'Optional lightweight context'). They add no meaningful guidance beyond stating optionality. No examples or constraints are provided, leaving the agent uncertain about what values to supply.

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's action ('Revoke an existing public snapshot report link') and the resource ('shareable report'). It distinguishes from siblings like create_shareable_report and update_shareable_report by the verb 'delete' and the specific mention of revocation.

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 includes a usage condition ('after the user explicitly asks to take it down'), which implies when to use. However, it lacks explicit guidance on when not to use or mention of alternatives like create_shareable_report vs delete.

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