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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Title discarded after the call,' but does not disclose return behavior, side effects, error conditions, or why the title is discarded. This is insufficient for a checker tool with no output schema.

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 and front-loads the main purpose clearly. However, the second sentence about discarding the title is of limited value given that no title parameter exists in the schema.

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 9 parameters, no required parameters, no output schema, and no annotations, the description is not complete enough. It does not specify which parameter contains the Wikipedia title, what the expected output/return is, or how to distinguish a true/false result.

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 references a 'title' but the input schema has no title or wiki-title parameter; it exposes ref, url, city, feed, host, json, path, zone, and query. Even though schema coverage is 100%, the description actively misrepresents the expected input and adds no useful parameter guidance.

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: 'Check whether a Wikipedia title exists.' This is clear and matches the tool name, though it does not distinguish itself from siblings beyond the Wikipedia-specific framing.

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 sibling tools like web-fetch, normalize-url, or file-path-ok. It also does not state what kind of title input is expected or what makes this the right choice.

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