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

There are no annotations, so the description carries the transparency burden. It does disclose a meaningful behavior - the title is discarded after the call - which implies no retention. It does not disclose response shape, failure behavior, network dependency, or how existence is determined.

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?

Two short sentences, front-loaded with the main intent, with no filler. The second sentence is an extra behavioral note that earns its place despite being incomplete.

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 simple existence check with no annotations or output schema, the description should at least say how to pass the title and what a successful reply means. It does neither, so the tool cannot be reliably invoked despite its apparent simplicity.

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 schema documents all seven properties, but none is a Wikipedia title; descriptions for `ref` and `path` explicitly call them Git/file paths. The description adds the 'title' concept without mapping it to a parameter, so an agent cannot tell what to supply.

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 verb and resource: it checks whether a Wikipedia title exists. That is clear and distinct from all sibling tools. However, the schema exposes no property that carries the title, so the stated purpose does not map onto the callable inputs cleanly.

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 on when to prefer this tool over alternatives or what context calls for it. The only sentence beyond the purpose is a disposal note, not usage direction.

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