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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the note 'Title discarded after the call,' which signals a stateless/privacy-conscious behavior. It does not disclose return behavior, auth requirements, or error handling, but the annotations lower the bar.

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 a single concise sentence that front-loads the core purpose: 'Check whether a Wikipedia title exists.' The second clause 'Title discarded after the call' is slightly cryptic but adds a behavioral note without unnecessary fluff. It is appropriately sized for the simplicity of the tool.

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?

There is no output schema, yet the description does not state what the tool returns (e.g., boolean, error, or object). It also fails to clarify that the many non-title schema properties are irrelevant, which could mislead an agent into populating unnecessary fields. For a deceptively simple tool, the description leaves important gaps in invocation and result interpretation.

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?

The input schema provides descriptions for all 15 properties, including explicit 'Wikipedia page title to check' for the title parameter, making schema coverage effectively 100%. The description adds no parameter information beyond this. With high schema coverage, a baseline of 3 is appropriate; the description does not clarify that only the title field is relevant despite the other schema entries.

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 states a specific action ('Check whether a Wikipedia title exists') and a clear resource (Wikipedia title). However, it does not explicitly differentiate from sibling tools like browser-url-ok or fetch-status, and the input schema includes many unrelated fields that could muddy the resource definition.

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 description provides no guidance on when to use this tool versus the many sibling tools. It does not state conditions like 'Use when you need to verify a Wikipedia page exists' or mention alternatives for URL or other checks. The agent is left to infer selection entirely from the tool name.

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