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

With no annotations, the description carries the behavioral burden. It does disclose one useful trait beyond the schema: 'Title discarded after the call.' However, it does not state the return type, whether a network lookup is performed, or what happens when the title does not exist.

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 the purpose front-loaded and the discard behavior called out separately. Every clause earns its place and there is no filler.

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 seven loosely related optional parameters and no output schema, the description is insufficient: it does not say which parameter carries the Wikipedia title, what the return looks like, or when to prefer this tool over sibling checks. The discard note is the only extra context preventing a lower score.

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 already describes all seven parameters in detail, so the high schema coverage sets a baseline of 3. The description adds no parameter-level meaning and, more problematically, refers to a 'title' that does not map to any property in the input schema.

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 uses a specific verb ('Check') and resource ('whether a Wikipedia title exists'), so the core operation is clear. However, it does not differentiate from sibling validation tools, and it introduces a 'title' concept that does not appear in the input schema.

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 about when to use this tool versus alternatives such as browser-url-ok, validate-json, or domain-shape. No exclusions, prerequisites, or routing conditions are provided; the only usage signal is implicit in the purpose statement.

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