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

With no annotations, the description must disclose behavior. It only states 'Title discarded after the call,' which is minor. More importantly, the description claims a Wikipedia-title check, but the parameter descriptions (e.g., 'discarded after the shape check') imply a generic validation tool. This misrepresentation means the agent cannot trust what the tool actually does.

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 one sentence, which is concise, but it is under-specified rather than appropriately brief. It fails to include essential information about how to invoke the tool, making the brevity detrimental rather than helpful.

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 the tool has 9 parameters, no annotations, and no output schema, the description is grossly inadequate. It does not explain the input format, the expected return value, or how the parameters relate to the stated purpose. An agent has no way to call this tool correctly.

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?

While schema description coverage is 100%, the parameter descriptions are inconsistent with the tool's stated purpose. None of the parameters is clearly the Wikipedia title, and the notes like 'discarded after the shape check' suggest a different function. The description adds no clarity about which parameter to use for the title check.

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 verb and resource ('Check whether a Wikipedia title exists'), but the input schema does not include a title parameter, and the parameters (ref, url, city, etc.) suggest the tool is actually a generic shape checker. This mismatch undermines the clarity of what the tool does, as an agent cannot determine how to supply the title.

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 siblings. The description does not mention alternatives, exclusions, or contextual triggers, leaving the agent without any basis for selection.

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