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

The description adds a useful data-handling detail beyond the annotations: 'Title discarded after the call.' This gives the agent some privacy/state context. However, it does not explain error behavior, response semantics, or why readOnlyHint is false for what appears to be a read-only check.

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 concise, with the main purpose front-loaded and a short behavioral note in the second sentence. There is no filler, though the lack of parameter mapping is a substantive gap rather than a style issue.

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 definition is incomplete for correct invocation: the description promises a Wikipedia-title check, but the schema offers no title input and the other parameters appear unrelated. Even with the output schema indicating a boolean result, an agent cannot reliably construct a valid call.

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 exposes parameters like ref, url, city, feed, host, json, and path, but none of them is a Wikipedia title. The description never maps the word 'title' to any schema property, so an agent cannot determine what input to provide. Schema description coverage is only 50%, and the description does not compensate for the missing title parameter.

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 clear action and resource: 'Check whether a Wikipedia title exists.' It aligns with the tool name and is understandable on its own. However, it does not distinguish this tool from sibling check-style tools, and the input schema makes it unclear which parameter represents the title.

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 like fetch-status, web-fetch, or normalize-url. The description only states the action without any context about prerequisites, exclusions, or preferred scenarios.

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