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

With no annotations, the description must carry the behavioral burden, but it only says 'Title discarded after the call' while no title parameter exists. It does not disclose output values, error behavior, side effects, or what 'exists' means. No annotation contradiction occurs because annotations are absent.

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 the main claim is front-loaded, but it is under-specified for a nine-parameter tool. The second sentence refers to a nonexistent title parameter and therefore does not earn its place.

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 nine unannotated parameters and no output schema, this description is far too incomplete: it does not say which parameter to provide, what result the agent will receive, or how this tool differs from the many sibling validators.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds no useful parameter meaning; it invents a title input absent from the schema. This active mismatch with the provided properties lowers the score below the schema-coverage baseline.

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 'Check whether a Wikipedia title exists,' but the input schema exposes no title parameter—only ref, url, city, feed, host, json, path, zone, and query. This mismatch makes the stated purpose misleading rather than clarifying.

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 instead of siblings like normalize-url, validate-json, rfc-number-ok, or search-query-len. Worse, the only purpose it suggests (Wikipedia title check) cannot be mapped to any available parameter, so an agent cannot select or invoke it correctly.

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