Restore an expired Temp

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

Discloses key behavioral traits: reactivation with same URL, time limit, and credential fallback. However, it omits details on side effects (e.g., overwriting), error conditions, and safety implications. Without annotations, this is partially adequate.

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 with no wasted words. Front-loaded with the main action and immediately follows with constraints and behavior. Every part earns its place.

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?

Despite clarity on core function, the description lacks details on return value, error handling (e.g., expiry beyond 7 days), and full parameter behavior. Given no annotations or output schema, the tool is not fully specified for safe invocation without additional probing.

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 low (33%) with only project_dir described. The description adds meaning by noting that credentials are read from .tempmd when omitted, implying optionality for temp_id and update_token. Still, temp_id and update_token remain undocumented in both schema and description.

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 reactivates an expired Temp with the same canonical URL, specifying the constraint of 7-day expiry window and credential fallback. This distinguishes it from siblings like publish_temp (create new) or update_temp (modify existing).

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?

Describes when to use (within 7 days of expiry) but does not explicitly state when not to use or provide alternatives. Implied from sibling names but lacks direct guidance for choosing between restore and publish/update.

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