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

The description discloses that the 'title' is discarded after the call, which is a useful behavioral hint. However, there is no mention of return values, error behavior, or the fact that the schema contains no 'title' parameter, making the actual operation opaque. With no annotations, the description carries the full burden but fails to clarify what happens beyond the discard note.

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, short sentence, which is concise and front-loaded with the core purpose. However, it omits critical details about how the title is supplied and what the tool does beyond discarding it, making the conciseness a detriment rather than an asset.

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 9 parameters, none required, and no output schema, the description is grossly incomplete. It does not explain which parameter holds the Wikipedia title, what constitutes a valid title, or what the result of the check is. The agent cannot correctly invoke the tool based on this 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 each parameter has a description in the schema. However, the tool description does not map any parameter to the 'title' it claims to check. The mention of 'Title' is disconnected from the schema's parameters (ref, url, city, etc.), which are unrelated to Wikipedia titles. The description adds no useful parameter semantics and actively confuses the mapping.

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 clear purpose: 'Check whether a Wikipedia title exists.' The verb 'check' and resource 'Wikipedia title' are specific. However, it does not distinguish from sibling check tools like file-path-ok or browser-url-ok, and the schema has no 'title' parameter, which creates ambiguity about what is actually being checked.

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 on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or alternative tools, leaving the agent to guess based on the name alone.

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