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

Goes well beyond the annotations by disclosing key side effects: the link is short-lived and one-time, no card is added, and 'makes the previous view link invalid.' It also flags token secrecy handling ('never show or put it in a URL'). This is genuine behavioral context not derivable from readOnlyHint=false / idempotentHint=false.

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?

Four short sentences, front-loaded with the action and result, then usage condition, then the parameter handling and side effect. No filler, every sentence 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?

An output schema exists, so return values need no explanation. For a mutation-style operation with annotations present, the description supplies the missing pieces: when to use it, the secret-handling requirement, and the invalidation side effect.

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 carries the burden. It adds meaningful semantics by labeling workspace_token 'private' and mandating it be passed as a tool argument rather than embedded in a URL. It stops short of describing format beyond what the schema pattern already encodes.

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?

States a specific verb ('Issue') and resource ('a new short-lived, one-time mobile or desktop web link for the existing guest shelf'), plus the scope (existing shelf). An agent can distinguish this from sibling tools like create_knowledge_bundle_drafts or claim_guest_knowledge_workspace by the resource alone.

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 constrains usage: 'Use only when the person asks to open or recover that shelf.' This is clear when-to-use guidance, though it does not name a specific alternative tool to use in other cases, keeping it short of a 5.

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