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

With no annotations present, the description must carry the behavioral burden. It does disclose that the title is 'discarded after the call', a useful privacy trait. However, it does not reveal whether the tool performs a network request, what it returns, or how missing titles are handled, leaving significant behavioral unknowns.

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 only two sentences and front-loads the core purpose in the first sentence. The second sentence adds a meaningful behavioral note without unnecessary detail. It is appropriately concise, though the schema mismatch makes the overall definition confusing.

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?

The tool description cannot be used to make a valid call: it mentions a title input that is absent from the schema, provides no output schema or return type, and offers no explanation of how the parameters relate to the operation. The only contextual snippet is the discarding statement, which is insufficient. An agent would have no idea how to invoke this 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 schema lists seven parameters (ref, url, city, feed, host, json, path), none of which is 'title' or even plausibly maps to a Wikipedia title. The description introduces 'title' without connecting it to any schema parameter. Schema descriptions like 'HTTPS URL to normalize or cite' are completely unrelated to checking Wikipedia titles, so the agent cannot determine what to pass.

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 is specific: 'Check whether a Wikipedia title exists.' This clearly identifies the verb (check), the resource (Wikipedia title), and the intended operation (existence verification). It also differentiates the tool from siblings like 'validate-json' or 'normalize-url', which address other domains.

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 when-to-use or when-not-to-use context, no prerequisites, and no exclusions relative to sibling tools. The only implied guidance is that the tool is for Wikipedia title existence checks, but the agent receives no direction about when to choose this over a search or citation tool.

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