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

With no annotations, the description carries the full burden of behavioral disclosure. It adds the trait that the title is discarded, but it does not disclose whether this is a remote network call, a local shape check, whether it is read-only, or what happens on failure. The provided disclosure is too thin for safe autonomous invocation.

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 with no filler. The core action is front-loaded, and the disposal note is a useful addition. It is appropriately concise for the information it conveys.

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?

This tool has nine optional parameters, no output schema, no annotations, and no parameter mapping in the description. A caller cannot determine which argument to supply, what the return value means, whether network access occurs, or how to interpret failure. The description is far too incomplete for correct invocation.

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 has 100% description coverage, the descriptions are generic and unrelated to Wikipedia titles. More importantly, the description never identifies which of the nine optional parameters represents the title, and none of the parameter names is 'title'. This makes it impossible for an agent to know what value to pass.

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 names a specific action and resource: 'Check whether a Wikipedia title exists.' This is reasonably clear and not a tautology. However, it does not distinguish this tool from sibling 'ok'/'shape' tools, and 'exists' is ambiguous between a live lookup and a format/shape validation.

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 gives no guidance on when to use this tool versus alternatives such as browser-url-ok, domain-shape, or file-path-ok. There is no stated context, prerequisite, or exclusion, so an agent must guess when this tool is appropriate.

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