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

The description mentions 'Title discarded after the call', which hints at data retention, but it does not clarify side effects, permissions, or what happens on success/failure. Moreover, the schema describes parameters that are 'discarded' in unrelated contexts, creating confusion about the tool's actual behavior.

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 (one sentence), which is efficient. However, the brevity omits critical information and the schema mismatch is not addressed, so conciseness does not contribute to clarity.

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 description is grossly incomplete. It does not specify return values, output format, error handling, or how the title is supplied. Combined with the irrelevant schema, an agent cannot infer proper usage or expected behavior.

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?

All 9 schema parameters have generic, unrelated descriptions (e.g., 'Git ref name', 'HTTPS URL', 'City name') that do not connect to the stated purpose of checking a Wikipedia title. There is no parameter for 'title', so the semantics are completely misaligned and misleading.

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 clear purpose ('Check whether a Wikipedia title exists'), but the input schema contains no 'title' parameter—only unrelated generic fields like ref, url, city, feed, etc. This mismatch makes the actual purpose ambiguous and undermines clarity.

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 guidelines are provided. There is no explanation of how to pass the title, when this tool should be used, any prerequisites, or example calls. The one-line description is insufficient for an agent to know how to invoke it correctly.

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