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

The description states 'Title discarded after the call,' which indicates a data-handling behavior. However, this is inconsistent with the schema, which contains no 'title' parameter. No other behavioral traits (e.g., read-only, side effects, permissions) are disclosed, and annotations are absent, so the transparency is minimal and confusing.

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, using a single sentence to convey the core purpose. It is front-loaded and easy to parse, with no filler or unnecessary details. This is an ideal length for a simple tool description.

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?

Given the tool has no output schema and low complexity, the description provides the basic purpose. However, the mismatched input schema creates significant confusion about expected parameters, and there is no explanation of how the check is performed or what constitutes a valid title. The description is incomplete in the context of the full tool definition.

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 description text adds no meaning about parameters. While the schema descriptions claim 100% coverage, they are absurdly mismatched (e.g., 'ref' for Git refs, 'city' for weather hints) and do not relate to checking Wikipedia titles. The description fails to clarify what input is actually expected, making it impossible to understand parameter usage.

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 clearly states the tool's purpose: to check whether a Wikipedia title exists. The verb 'check' and object 'Wikipedia title exists' are specific. However, it does not mention scope or distinguish itself from related tools like fetch-status or normalize-url, leaving some ambiguity about its exact role.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of preferred scenarios, limitations, or relationships to sibling tools. Users are left to infer appropriate usage without any contextual hints.

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