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

Annotations already declare openWorldHint=true and destructiveHint=true, so the agent knows this grants outward access. The description adds genuinely useful context that results and balances are never exposed, but it does not explain why the operation is flagged destructive, whether links can be revoked, or what the returned link looks like.

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 short sentences with no filler, and the privacy constraint is front-loaded right after the core action. Nothing is redundant, though nothing is devoted to invocation guidance either.

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 five-parameter mutation with no parameter descriptions, no output schema, and a destructive annotation, the description is thin. It never says how an agent should obtain the required ast hash, how long the link lasts by default, or what happens to previously issued links.

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 coverage is 0%, so the description must carry parameter meaning and does not: spec_id, revision_id, expected_ast_hash, expires_seconds and include_context are all undescribed in both places. The phrase 'saved request' hints at the spec/revision pairing, but the required 64-hex expected_ast_hash and the 1-hour-to-30-day expiry window are left entirely unexplained.

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?

It names a specific verb and resource ('Creates a link to the wording and conditions of a saved request'), which is clear enough for an agent to distinguish it from share_find or share_collection. It stops short of naming a sibling or stating scope limits (e.g. link lifetime, who can open it).

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 second sentence implies a use case by clarifying what the link exposes, which helps an agent decide it is safe to share logic but not data. There is no explicit when-to-use, no mention of prerequisites, and no routing to revoke_spec_link or get_shared_spec for related operations.

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