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

With no annotations present, the description carries the full burden. It does disclose that the title is discarded after the call, implying no persistent side effect, and the check is read-only in nature. However, it does not mention whether the check involves a network request, what happens on invalid input, or any rate-limiting or error behavior, leaving moderate gaps.

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 a single sentence that conveys the core purpose and a useful behavioral note. There is no redundancy or filler, and all content earns 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?

No output schema is provided, yet the description does not specify what the tool returns (e.g., boolean, success indicator). The schema contains many seemingly unrelated parameters, and the description does not clarify that only 'title' should be used or that other parameters are ignored. An agent may be uncertain how to invoke and interpret the tool 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 input schema provides descriptions for every parameter, so schema coverage is high. The tool description adds minimal parameter-level insight beyond confirming that the 'title' parameter is the relevant one; the note about discarding the title is behavioral rather than semantic. This meets the baseline but does not elevate it.

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 ('Check whether a Wikipedia title exists') and a clear resource. It is not a tautology and is distinct from sibling tools like domain-shape or jira-key-shape. However, it does not explicitly differentiate itself from siblings or name any alternatives, so it does not reach a 5.

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 provided about when to use this tool versus alternatives. Sibling tools such as fetch-status or validate-json exist, but the description gives no context on when this tool is preferred. This leaves the agent to infer usage from the name and purpose alone.

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