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

The phrase 'Title discarded after the call' hints at statelessness but does not clarify side effects, return values, or error behavior. Without annotations, this minimal note is insufficient for understanding the tool's full behavior.

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 very short and economical, but the mismatch between the stated purpose and the schema makes it less effective. It is not verbose, yet it fails to align with the input schema.

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 description omits critical details such as the expected return value (e.g., boolean) and does not address the actual parameters. The mismatch with the schema leaves an agent without enough information to invoke the 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?

The description implies a single 'title' parameter, but the schema lists nine unrelated parameters (ref, url, city, etc.) with generic descriptions. The description adds no meaning to the actual parameters and contradicts the schema's parameter list.

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 a specific verb and resource: 'Check whether a Wikipedia title exists.' This distinguishes it from sibling tools like browser-url-ok or file-path-ok, though the schema does not contain a 'title' parameter.

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 such as search-query-len or normalize-url. The description does not mention any conditions or context that would direct an agent to pick this tool.

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