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

With no annotations, the description carries the full burden. It discloses that the title is 'discarded after the call' but does not state what the check returns, whether it is read-only, any permissions needed, or error behavior. The single behavioral note is insufficient.

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 brief and front-loaded with the core purpose. However, its brevity borders on under-specification, and the sentence about discarding the title adds little clarity. It is concise but not informative enough.

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 nine parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain how to pass the title, what the expected response is, or how the parameters relate to the check. The agent cannot correctly invoke this tool based on the provided information.

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 schema description coverage is 100%, each parameter's description is generic and unrelated to Wikipedia titles (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no meaning about which parameter corresponds to the title, and the schema itself suggests a different purpose, so the parameter semantics are misleading.

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'), but the input schema contains no 'title' parameter and instead lists nine unrelated generic fields (ref, url, city, etc.). This mismatch makes it impossible for an agent to know how to provide the title, so the purpose is not actionable.

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 use this tool versus its many siblings (e.g., domain-shape, browser-url-ok). The description does not mention any conditions or alternatives, leaving the agent to guess the appropriate context.

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