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

With no annotations provided, the description carries the full burden. It mentions that the title is discarded, which hints at no persistence, but it does not disclose whether the check performs network access, whether it is read-only, what side effects occur, or what error/response behavior to expect.

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 extremely concise, consisting of two short sentences with no filler or redundant wording. It is well within acceptable length.

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?

There is no output schema, no required parameter indicating the title to check, no explanation of what the return value means, and no mention of failure conditions. The mismatch between the stated purpose and the actual schema makes the tool effectively unusable without external knowledge.

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 contains nine optional string parameters, but none of them represent a Wikipedia title. The descriptions are unrelated to the stated purpose (e.g., 'Git ref name', 'HTTPS URL to normalize or cite'), so the agent cannot determine which parameter to populate for the title check.

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 object: 'Check whether a Wikipedia title exists.' However, it does not identify which input parameter supplies the title, and the follow-up 'Title discarded after the call' is ambiguous about what title is being referenced.

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 any of the many sibling tools such as fetch-status, normalize-url, or search-query-len. The description provides no context for selection.

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