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

There are no annotations, so the description carries the behavioral disclosure burden. 'Title discarded after the call' is a useful privacy/retention note. However, the description does not state whether the call is read-only, what happens for missing titles, whether a network request is made, or what output is returned.

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, front-loaded, and contains no filler. The purpose appears immediately and the discarded-title note is a valid second sentence. The brevity is helpful, but it omits the critical parameter mapping.

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 validation tool with no output schema and no annotations, the description should say what result to expect and how to supply the title. Neither is present, and the mismatched input schema makes the tool incomplete to invoke 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 schema describes all eight parameters, but none is described as the Wikipedia title. The generic fields such as 'ref', 'city', 'feed', and 'json' appear unrelated to title existence checking, and the description does not map the title to any input. An agent cannot reliably know which parameter 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 is specific: it says the tool checks whether a Wikipedia title exists. This clearly differentiates the purpose from sibling tools like web-fetch or fetch-status. However, it does not explain what parameter carries the title, and the input schema has no 'title' field.

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?

No guidance is given about when to use this tool versus alternatives. With many similar shape-check and status tools available, an agent cannot tell from the description why wiki-title-ok is the correct choice. Usage context must be inferred entirely from the tool name.

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