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

With no annotations, the description carries the full burden. It notes that the title is discarded after the call, a privacy/behavioral detail, but it does not disclose that the tool likely makes a network request to Wikipedia, nor does it mention error behavior, rate limits, or side effects. The single behavioral note is minimal.

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 extremely short (two sentences) but not concise in a useful way. It omits essential information about input parameters and return values, making it under-specified rather than efficiently concise.

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?

The tool has 9 parameters, none required, no output schema, and no usage guidance. The description does not explain what the tool returns, how to invoke it correctly, or what the expected input is. For a tool with such a large parameter surface, this is completely inadequate.

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?

Despite 100% schema description coverage, none of the parameter descriptions mention 'title' or align with the tool's stated purpose. The description itself does not map any parameter to the Wikipedia title, leaving the agent unable to determine which input to provide. This is a critical 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 clearly states the tool's function: 'Check whether a Wikipedia title exists.' This is a specific verb+resource and distinguishes it from sibling tools like 'browser-url-ok' or 'domain-shape'. However, it does not indicate which parameter carries the Wikipedia title, leaving invocation ambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, alternatives, or exclusions. The agent is left to infer usage from the name alone, which is insufficient.

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