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

No annotations are present, so the description carries the full burden. It discloses that the title is discarded after the call, which is a useful privacy-related detail, but it omits network behavior, auth requirements, error handling, and what the tool actually returns.

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 the purpose front-loaded and an additional behavioral detail about discarding the title. It is efficient, though the brevity contributes to the missing invocation information.

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?

With no output schema, no annotations, seven unrelated parameters, and only a one-line description, the tool is not complete enough for an agent to call correctly. It lacks the crucial mapping from purpose to inputs and the expected return contract.

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 the 'title' concept to any of the seven input parameters. The schema documents each parameter, but none of those descriptions plausibly represent a Wikipedia title, leaving the agent unable to determine which field to populate.

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 action and resource: checking whether a Wikipedia title exists. It is not a tautology, and the core purpose is clear, though it does not explicitly differentiate itself from sibling URL or citation tools.

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, and no mention of prerequisites or exclusions. The only usage signal is implied by the purpose phrase, which is not enough for an agent to choose it confidently over siblings like citation or web-fetch.

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