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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It only states that the 'title' is discarded after the call, but since no parameter is identified as the title, this is confusing. It does not disclose whether the operation is read-only, whether it makes network calls, or what happens on failure, leaving critical behavior opaque.

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 concise at two sentences, but it is under-specified rather than efficiently structured. It front-loads the purpose but immediately introduces an undefined 'title' concept without context. There is no logical flow to guide the agent, and the mention of 'discarded' is premature given the ambiguity.

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?

This tool has 9 parameters, no output schema, and no annotations, yet the description is only one line of actual instruction. It does not explain which parameter is the title, how existence is determined, what the return value indicates, or any edge cases. An agent cannot reliably invoke this tool correctly with the given information, making it severely incomplete.

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 provides 100% description coverage for all 9 parameters, so the baseline is 3. The tool description adds no additional meaning to these parameters—it doesn't explain which parameter represents the Wikipedia title or how the parameters interact. The parameter descriptions themselves are generic and unrelated to Wikipedia, so the tool description fails to bridge the gap.

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 verb and resource ('Check whether a Wikipedia title exists'), so the basic purpose is discernible. However, it fails to map that purpose to any of the 9 input parameters—none of which is labeled as a title—making it unclear how the tool is actually invoked. It also doesn't distinguish itself from sibling tools like browser-url-ok or domain-shape, which follow similar check-style patterns.

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 provided on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions, and the sibling list includes many similar 'shape' or 'ok' checks, so an agent has no basis to select this tool over others.

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