delete_qurl

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

Description states immediate invalidation, which is behavioral. But does not mention reversibility, permissions, or side effects. No annotations to supplement, so description partially fulfills but lacks depth.

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?

Two concise sentences, directly stating purpose and immediate effect. No fluff, front-loaded.

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?

Adequate for a simple delete operation, but lacks mention of return value or error handling. No output schema to supplement. Could be more complete.

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 for resource_id is detailed (must start with r_, does not accept q_ IDs). Tool description does not add parameter-level info beyond that, so baseline of 3.

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?

Clearly states the tool revokes/deletes a qURL and that it immediately invalidates the link. Different from siblings which create, extend, get, list, etc.

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?

Description lacks explicit when/when-not to use this tool vs alternatives like update_qurl or extend_qurl. Only implicit that it's for deletion. The schema description gives a constraint on ID format but no usage guidance.

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