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

The line 'Title discarded after the call.' does disclose a behavioral trait beyond the annotations, namely that the title input is not retained. Since no annotations are provided, the description carries the burden, but it does not mention whether the tool calls Wikipedia, what it returns, or how failures behave. The disclosure is meaningful but thin.

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 two short sentences, front-loaded with the purpose and followed by a disposal note. There is no fluff and each sentence contributes information. The brevity is efficient, though it contributes to a broader under-specification problem captured under other dimensions.

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?

With no output schema and no annotations, the description must explain the input mapping and return behavior itself. It provides neither: the title is implied but absent from the input schema, and the return value is only vaguely implied by 'exists.' This is not enough for an agent 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 properties each have descriptions, but none of them is a 'title' and the description never maps 'Wikipedia title' to a specific field. An agent cannot tell whether to pass url, feed, or some other value, or whether the title is expected outside the schema. The disposal statement adds no parameter-binding value.

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 concrete action and resource: 'Check whether a Wikipedia title exists.' This is a specific verb-plus-resource statement, not a tautology, and it helps distinguish the tool from the sibling shape/validation tools. However, it never connects the purpose to any of the seven schema properties, so full clarity is not achieved.

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 versus siblings such as browser-url-ok, normalize-url, or validate-json. The description gives no context, exclusions, or alternative conditions, so the agent receives no routing help.

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