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

The description and parameter descriptions repeatedly state that inputs are 'discarded after the call,' which adds a data-handling trait not present in annotations. However, annotations provide no clear safety profile (readOnlyHint=false, destructiveHint=false), and the description does not disclose whether a network call occurs, what side effects exist, or what a result 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?

The description is two short sentences, front-loaded with the operation and with no filler. The discard note is a useful behavioral detail that 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?

For a tool with no output schema, the description must explain expected return values and required input, but it does neither. The title-to-parameter mismatch and lack of return/error information leave critical gaps for an agent attempting to call it correctly.

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?

Although the schema properties all have descriptions, none describes a 'title' parameter. The description names 'a Wikipedia title' without mapping it to any schema field, and the parameter descriptions only say values are discarded, so the agent cannot determine which parameter carries the title to check.

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 uses a specific verb and resource: 'Check whether a Wikipedia title exists.' This clearly states the tool's core function and differentiates it from sibling tools like normalize-url or validate-json by focusing on Wikipedia title existence.

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?

There is no guidance about when to prefer this tool over siblings (e.g., web-fetch, normalize-url, domain-shape) or any conditions or exclusions. The purpose statement implies a use case, but the definition never says when-not to use it or names alternatives.

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