extend_qurl

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

Discloses automatic resolution of q_ IDs to parent resource, and implies mutation by extending expiration. No annotations exist, so the description carries full burden. It does not mention error handling or if the qURL must be active beyond the word 'active'.

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 sentences, front-loaded with purpose, no redundant or vague phrasing. Every word adds value.

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 no output schema and simple parameters, the description covers the main behavior and alternatives. Could mention potential error conditions or constraints (e.g., max extension), but overall adequate.

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% and schema descriptions are thorough. The description adds minimal new information beyond paraphrasing the schema (e.g., 'resource ID (r_) or qURL display ID (q_)'). Baseline 3 is appropriate.

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 verb 'extend' and the resource 'expiration of an active qURL', and distinguishes itself from the sibling tool update_qurl by positioning as a shorthand for simpler updates.

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?

Explicitly advises when to use this tool versus update_qurl: 'Shorthand for update_qurl with only extend_by — use update_qurl for richer updates.' This provides clear usage guidance.

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