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

The description adds a privacy-relevant behavioral note that the title is 'discarded after the call,' but no annotations exist to cover side effects, return behavior, or failure modes. It also references a 'title' that does not actually appear as a parameter in the input schema, weakening the behavioral clarity.

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 short and front-loaded, with no wasted words. However, it is under-specified for a tool with seven parameters and no output schema, so the brevity comes at the cost of completeness.

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 seven-parameter schema, no output schema, and no annotations, this description is far too thin. It omits the critical title-to-parameter mapping, return type, error behavior, and usage context, so an agent cannot reliably select or invoke the tool.

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 explain how any of the seven schema parameters relate to the 'Wikipedia title' being checked. The word 'title' is absent from the input schema, so an agent cannot determine which parameter supplies the title or how the other unrelated-looking parameters are used.

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 verb and resource: 'Check whether a Wikipedia title exists.' This clearly identifies the tool's core purpose and distinguishes it from URL-shape or fetch-status siblings. However, it does not explicitly describe the return value or differentiate among siblings that might also handle Wikipedia-related checks.

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 gives no guidance about when to use this tool versus other shape-check or status-check tools in the sibling list, nor when not to use it. The intended use case is only implied by the tool name and the single stated purpose.

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