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

Since there are no annotations, the description must carry the behavioral load. It successfully communicates the state change (unavailability), which is a key behavioral trait for a revocation function.

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 perfectly concise. It delivers the action and the consequence in a single, impactful sentence, front-loading the core information without unnecessary filler.

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?

For a low-complexity tool with no output schema, the description is highly complete. It addresses the 'what' and the immediate 'result' which is all an agent needs to decide whether to invoke it.

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?

While the description doesn't add complex semantic meaning to the parameter, it provides crucial context that the tool operates on a 'photo share link,' grounding the abstract 'share_id' parameter into a concrete domain.

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 is extremely clear, using strong verbs like 'Turn... off' and specifically naming the resource: 'photo share link.' This leaves no ambiguity about the tool's function.

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?

It clearly defines the outcome of the tool (the link becomes unavailable to future viewers), which serves as a strong usage guideline for when the agent should choose this function over merely viewing or listing links.

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