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

Adds real value beyond annotations: it discloses that the lookup is re-run unchanged and will yield the same result, which prevents a wasted retry loop. However, annotations declare destructiveHint=true and idempotentHint=false, and the description never mentions that a refresh can overwrite existing or already-corrected metadata — the destructive aspect is undisclosed. The 'same result as before' framing also sits awkwardly against idempotentHint=false, though not enough to be a contradiction.

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?

Three sentences, front-loaded with what it does, then the caveat, then the redirect. Efficient overall; the last sentence runs long by carrying both the alternative and the rationale.

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?

No output schema and only 3 simple params, so the description carries the semantic burden well, including ambiguous-match behavior and the relink path. The one omission an agent operating under destructiveHint=true would want — what existing data gets overwritten — is unaddressed.

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 100%, so title vs item_id precedence and the candidate-on-ambiguous-match behavior are already fully documented in the schema. The description adds no further parameter meaning, so the baseline of 3 applies.

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 and resource (re-fetch metadata from external sources) plus the exact condition (item data incomplete), and explicitly contrasts itself with edit_item. An agent can separate it from the ~56 siblings without opening a schema.

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?

Gives when-to-use (incomplete data), an explicit when-not (it does NOT fix a wrong match), and names the correct alternative with the exact tool and parameter (edit_item with new_external_id). This is the strongest kind of routing guidance.

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