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

The only behavioral disclosure is 'Title discarded after the call,' which indicates the input is not persisted. However, with no annotations present, the description should also clarify whether the operation is read-only, makes network requests, or has any side effects. This minimal disclosure is insufficient for a tool with zero annotation coverage.

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 a single sentence with no fluff. It is efficient and to the point. However, it is too brief to be considered excellent, as it omits crucial details, but for conciseness alone it is well-structured.

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's complexity (9 parameters, none required, no output schema, no annotations), the description is vastly incomplete. It fails to explain how the parameters relate to the purpose, what the tool returns, how to invoke it, or any side effects. An agent would be unable to correctly select or call this tool based solely on the description and schema.

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 does not connect any of the 9 parameters to its purpose. None of the parameter names or schema descriptions mention a Wikipedia title; parameters like 'url', 'city', 'feed', and 'path' seem unrelated to the stated function. The description adds no meaning beyond the schema, and in fact there is a severe mismatch between the stated purpose and the parameters, making it impossible to infer which parameter is the title.

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: checking whether a Wikipedia title exists. The verb 'check' and the resource 'Wikipedia title' make the purpose explicit, and it is distinct from sibling checkers like file-path-ok or browser-url-ok by the resource type. However, it does not explicitly contrast itself with any sibling, so it gets a 4 rather than 5.

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 alternatives. No mention of conditions, prerequisites, or scenarios where it should or should not be used. The description simply states what it does, offering no selection advice.

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