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

With no annotations provided, the description carries the full burden. It does disclose one behavioral trait—that the title is 'discarded after the call'—but it gives no indication of the return type, network dependency, error behavior, or any side effects. The discard note is a good start but insufficient for an agent to anticipate the tool's 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 a single sentence that is immediately readable and free of filler. The discard warning is arguably secondary but still relevant to privacy expectations. It earns points for brevity, though the extreme brevity contributes to the completeness problems.

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?

For a tool with seven parameters, no annotations, and no output schema, the description is far from complete. It fails to identify which parameter carries the Wikipedia title, what the response looks like, or what 'title exists' means in terms of status codes or booleans. An agent reading this description alone could not 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 mentions a 'Wikipedia title' but the input schema contains no 'title' property; it has generic fields like ref, url, city, feed, host, json, and path, none of which is described as the title. This creates a direct disconnect between the stated purpose and the actual parameters, so the description provides no help in selecting or filling the correct input. The schema descriptions themselves are generic and don't bridge this gap.

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 ('Check') and a clear resource ('whether a Wikipedia title exists'), which immediately distinguishes this from most sibling tools like validate-json or domain-shape. However, it doesn't clarify what form a 'title' takes or how it's supplied, and the name combined with the generic schema slightly blurs the purpose.

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 about when to use this tool versus alternatives, no mention of prerequisites (e.g., a Wikipedia page name), and no exclusion conditions. The description only states the action and a discard behavior, leaving the agent to infer any usage context from the tool name alone.

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