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

No annotations are provided, so the description carries the full burden. It mentions 'Title discarded after the call' which hints at statelessness, but this is minimal. It does not disclose expected outcomes (success/failure), error behavior, or any side effects. The description is under-specified for a tool with no annotation safety net.

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 sentence with no extraneous words. It is concise and front-loaded with the core action. However, it is so brief that it borders on under-specification, though the conciseness itself is good.

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?

Given 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain how to invoke the tool, which parameter is essential, what the response looks like, or how results are conveyed. An agent would struggle to call this tool correctly based on the description alone.

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?

Schema coverage is 100%, so the baseline is 3, but the parameter descriptions are generic and disconnected from the tool's stated purpose. For instance, 'ref' (Git ref), 'city' (weather hint), and 'feed' (RSS) have no clear relation to checking a Wikipedia title. The description does not clarify which parameter represents the title or how to use the schema, so it fails to add meaningful semantics.

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 clearly states the tool's action: 'Check whether a Wikipedia title exists.' It names a specific verb and resource, making the core purpose unambiguous. However, it does not differentiate from sibling validation tools like 'domain-shape' or 'file-path-ok' that follow the same 'shape check' pattern.

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 the many sibling tools (e.g., 'domain-shape', 'normalize-url', 'validate-json'). No context is given about typical use cases or alternatives, leaving the agent to infer applicability.

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