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

No annotations exist, so the description carries the full burden. It only mentions 'Title discarded after the call,' but there is no title parameter in the schema, making this note irrelevant and potentially confusing. No side effects, permissions, rate limits, or response behavior are disclosed.

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, which is concise in length, but it is severely under-specified. It does not explain the tool's behavior relative to its parameters, making it more of a placeholder than a helpful definition. The statement about discarding a title is not only irrelevant but also fails to earn its place.

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 nine parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain what the tool actually does with the parameters, what it returns, or when to use it. The agent cannot determine correct invocation from this definition alone.

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 schema description coverage is 100%, the parameter descriptions are generic (e.g., 'Git ref name', 'HTTPS URL') and do not connect to the stated purpose of checking a Wikipedia title. The tool description adds no meaning about how these parameters are used, and the mismatch between the description and schema leaves the agent without any semantic guidance.

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 purpose ('Check whether a Wikipedia title exists') that aligns with the tool name, but it directly contradicts the input schema, which lists nine generic parameters (ref, url, city, feed, etc.) unrelated to Wikipedia titles. This mismatch makes the purpose misleading rather than clear.

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 siblings (browser-url-ok, fetch-status, normalize-url, etc.). There are no conditions, exclusions, or alternative references, leaving the agent without any decision support.

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