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

No annotations are present, so the description carries the full burden of behavioral disclosure; it adds only 'Title discarded after the call,' a privacy/discard note. It does not disclose whether the tool hits Wikipedia's API, what happens when a title does not exist, whether any state is modified, or any rate-limit/error behavior. For a tool with no annotations, this is insufficient.

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 sentences with no filler and leads with the purpose, followed by a behavioral note. It is efficient and front-loaded, though the second sentence is vague enough that it could be clearer.

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 a seven-property input schema, no output schema, and no annotations, this description is far too thin: it never specifies the input shape, return value, or failure semantics. The mismatch between the description and the schema makes safe invocation impossible.

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?

Every schema property has a description, but none mentions a Wikipedia title, and the description adds no mapping to the single required piece of input. The schema properties describe Git refs, URLs, cities, feeds, hosts, JSON, and paths, which are unrelated to the stated purpose. An agent cannot tell 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 first sentence states a specific verb and resource: 'Check whether a Wikipedia title exists,' and the title-specific wording helps distinguish it from sibling URL/file/JSON checkers. However, the input schema contains no 'title' property and instead lists ref, url, city, feed, host, json, and path, so the stated purpose does not map to any declared input. The description is not a tautology, but it leaves the tool's actual contract unclear.

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 implies the tool is for verifying Wikipedia titles, so an agent can infer a use case. It does not explicitly state when to choose this over sibling shape-checkers or when not to use it, and no alternatives are named. The context is clear but the boundary conditions are left implicit.

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