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

No annotations are present, so the description must carry the full burden. It discloses that the title is discarded after the call, but this is also repeated in the schema descriptions. It does not mention the return value, whether it makes a network request, or what happens with the other schema parameters, leaving important behavioral traits 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 only two sentences and front-loads the primary purpose. There is no wasted wording, though the second sentence about discarding the title repeats information already visible in the schema, which slightly undermines its value.

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 seven schema parameters and no output schema or annotations, this description is far too minimal. It fails to explain which parameter to use for the title, what the check returns, error behavior, or network implications. An agent cannot reliably invoke this tool based on the definition 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?

The description adds no meaning about parameters and, critically, never identifies which parameter provides the Wikipedia title. The schema contains unrelated fields (ref, url, city, feed, host, json, path) with descriptions referencing 'shape check' or 'discarded', none of which connect to the stated purpose. Even though schema descriptions exist, they are incongruent with the tool's function.

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 action and resource: 'Check whether a Wikipedia title exists.' This clearly conveys what the tool does and distinguishes it from sibling tools like fetch-status or normalize-url, though it does not explicitly name alternatives.

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 implies the usage context: you would use this tool when you need to verify the existence of a Wikipedia title. However, it provides no explicit when-to-use guidance, exclusions, or comparison with alternatives such as fetch-status or browser-url-ok.

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