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

Annotations are absent, so the description carries the full burden. It only states 'Title discarded after the call,' which is irrelevant because no title parameter exists. It does not disclose what the tool actually returns, side effects, or how it checks existence. The description does not add meaningful behavioral context.

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 only two sentences, which is concise, but it is ineffective because it omits essential information about the parameters and does not align with the schema. Being short is not a virtue when the content is misleading; the description sacrifices clarity for brevity.

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 and no output schema, the description is severely incomplete. It does not specify return values, error handling, or which parameter is actually used for the title check. The mismatch between description and schema leaves an agent without enough information to invoke 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 schema provides descriptions for all 9 parameters (100% coverage), each with a clear purpose and note about being discarded. However, the tool description does not explain how these parameters relate to the stated purpose of checking a Wikipedia title. The description adds no value beyond the schema, and the mismatch between the title focus and the actual parameters creates confusion.

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 verb and resource ('Check whether a Wikipedia title exists'), which is clear in isolation. However, the input schema contains 9 parameters (ref, url, city, feed, etc.) with no 'title' parameter, so the actual tool purpose contradicts the description. This mismatch makes the tool's function ambiguous and misleading to an agent.

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 on when to use this tool versus the many sibling tools (e.g., normalize-url, browser-url-ok, web-fetch). The description does not mention any conditions, alternatives, or exclusions. An agent has no basis to select this tool over others.

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