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

No annotations are present, so the description carries the full burden of behavioral disclosure. The only behavioral detail is 'Title discarded after the call,' but there is no title parameter; nothing explains what 'exists' means, what the return value is, whether the call is read-only, or what happens with the other seven parameters.

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 very short, but compactness is achieved by omitting critical information. The sentence 'Title discarded after the call' is confusing because no title input exists, and the description lacks the structure needed to make seven schema parameters understandable.

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, no annotations, and no guidance on which of the seven parameters to supply or how to interpret the result. For a tool that ostensibly checks existence, the definition is materially incomplete and would not allow a model to invoke it reliably.

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 does provide descriptions for all seven parameters, which gives it a baseline level of semantic coverage. However, the tool description refers to a 'title' that is not among the parameters, and the listed params (ref, url, city, feed, host, json, path) appear unrelated to checking a Wikipedia title, leaving the agent without a clear parameter to populate.

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 an action ('Check') and an object ('Wikipedia title exists'), so it is not a pure tautology. However, the input schema exposes no title parameter, making the stated purpose unmappable to any callable input, and the description does not distinguish this tool from sibling validators like browser-url-ok or validate-json.

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?

No when-to-use guidance is provided, and no alternative tools are named or excluded. The only additional sentence about 'Title discarded' does not help an agent decide between this tool and a sibling shape checker.

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