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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions only that 'Title discarded after the call,' but the schema includes multiple parameters and varying discard/check behaviors (e.g., 'discarded after the shape check', 'discarded after the length check'). The description does not clarify what actually happens during the call—whether it validates existence, makes network requests, or simply performs shape validation. This is insufficient for an agent to predict side effects or safety.

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 very short (two sentences), which is concise, but it is not effectively structured. The first sentence states a purpose, the second mentions a discard behavior, but neither provides useful detail. While brevity is good, the content is too sparse to be helpful, so it earns a middle score.

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 9 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain the role of each parameter, how to achieve the stated outcome, or what the result indicates (e.g., boolean, error message). An agent cannot correctly invoke this tool based on the current description. It is completely inadequate for a multi-parameter tool of this complexity.

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?

Schema coverage is 100%, so the schema already describes each parameter. However, the description adds no clarity about how any parameter relates to the stated purpose of checking a Wikipedia title. There is no parameter that obviously corresponds to a Wikipedia title, and the description does not map parameters to the intended action. The description fails to add value beyond the schema and even introduces confusion by referencing a 'title' that does not appear in the schema.

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'), but the input schema has no parameter for a Wikipedia title (no 'title' field) and instead contains 9 unrelated parameters like 'ref', 'url', 'city', 'feed', etc. This mismatch makes the tool's actual purpose ambiguous and fails to distinguish it from sibling checker tools such as 'domain-shape' or 'file-path-ok'. The description misleads about what the tool does.

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. Sibling tools like 'search-query-len', 'normalize-url', and 'file-path-ok' appear to cover specific checks, but nothing here explains the intended context for this tool or which of its many parameters should be used for what purpose. An agent has no way to know if this is the correct tool for a given task.

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