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

With no annotations, the description carries full behavioral burden. It does disclose that the title is discarded after the call, implying statelessness, and 'check whether exists' suggests a read-only operation. But it omits return type, failure behavior, network dependence, and whether matching is exact.

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 two short sentences with no filler. The statelessness note earns its place, and the core purpose is front-loaded. It is concise, though it sacrifices some operational detail.

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 nine optional parameters, no output schema, no annotations, and no usage guidance, the description is not complete enough for confident invocation. It fails to explain what the result means, which parameter provides the title, or how this tool relates to alternatives.

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?

Schema coverage is 100%, so the parameters themselves are documented, but the description adds no mapping from the core 'title' concept to any property. None of the listed parameters is identified as the Wikipedia title, making it unclear what an agent should pass. The repeated 'discarded after the call' phrasing adds no parameter-level meaning.

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 operation: checking whether a Wikipedia title exists. This is clearly distinct from generic fetch or validation tools. However, it does not explain how the title is supplied, and the schema lists no explicit 'title' parameter, so the purpose lacks an operational anchor.

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 on when to use this tool instead of siblings such as web-fetch, normalize-url, or validate-json. There are no preconditions, examples, or exclusions, leaving the agent to guess the appropriate context.

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