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

There are no annotations to disclose side effects, permissions, or data retention. The only behavior mentioned is 'Title discarded after the call,' which is vague and not aligned with the actual parameters (no 'title' parameter exists in the schema). It fails to clarify whether the tool performs network requests, reads local data, or has any side effects, leaving the agent blind to potential impacts.

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 a single sentence, making it concise and front-loaded with the main purpose. It avoids verbose explanations and gets to the point quickly. However, it is perhaps too sparse to be fully effective, but for the purpose of conciseness alone, it performs well.

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?

The tool has 9 parameters and no output schema, yet the description provides almost no context on how these parameters relate to the action. It does not explain what constitutes a valid title, whether the check is case-sensitive, or what the return value indicates. The description is severely incomplete for an agent to use 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?

Although the schema provides descriptions for all 9 parameters, those descriptions are generic and clearly copied from other domains (e.g., 'Git ref name' for 'ref', 'HTTPS URL to normalize or cite' for 'url'). They do not relate to checking Wikipedia titles and likely mislead the agent. The coverage is technically 100%, but the semantic quality is almost nonexistent, offering no meaningful insight into how each parameter should be used.

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 function: 'Check whether a Wikipedia title exists.' It specifies a verb (check) and a resource (Wikipedia title), making the primary purpose unambiguous. However, it does not differentiate from sibling tools like browser-url-ok or file-path-ok, which also perform existence checks, so it misses the top score.

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 usage guidance is provided beyond the one-line description. The description does not indicate when to prefer this tool over alternatives, nor does it give context about typical use cases (e.g., verifying a link before citation). There is no mention of prerequisites or conditions for use, leaving the agent without direction on when to invoke this tool.

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