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

The description notes the title is discarded after the call, but provides no other side-effect information (e.g., read-only behavior, network access, caching). No annotations are available to supplement this, leaving most behavioral aspects undisclosed.

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 short and tightly worded, but its brevity sacrifices essential information. It fails to connect the tool's purpose to the provided schema, making the concise structure ineffective.

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?

With 9 parameters (none required) and no output schema or usage examples, an agent cannot determine how to invoke this tool correctly. The description does not bridge the gap between the stated 'check Wikipedia title' purpose and the concrete input/output behavior.

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 descriptions for parameters like 'ref', 'url', 'city', and 'feed' are generic and appear copied from other tools; none of them semantically map to a 'Wikipedia title'. The actual input needed for the described purpose is missing, so parameter semantics are nearly useless.

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 checks whether a Wikipedia title exists, but the input schema exposes 9 unrelated parameters (ref, url, city, etc.) and no obvious slot for the title, creating a mismatch that undermines clarity.

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?

No guidance is given about when to use this tool relative to its many siblings (e.g., fetch-status, normalize-url, search-query-len). The description does not mention any alternative or condition for selection.

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