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

No annotations are provided, so the description must carry the full behavioral burden. It merely mentions 'Title discarded after the call,' which is confusing given the lack of a title parameter, and says nothing about side effects, permissions, error behavior, or what the call actually does with the nine parameters.

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 short, but its brevity is not a virtue because it omits essential information and is misleading. It front-loads an irrelevant claim about discarding titles, wasting the only sentence on an unhelpful detail.

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 9 parameters, no output schema, and no annotations, the description is grossly incomplete. An agent cannot determine what input to provide, what the tool returns, or what side effects (if any) occur. The tool is effectively unusable from this description 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?

The schema descriptions are generic placeholders (e.g., 'Git ref name; discarded after the shape check') and do not relate to the stated purpose of checking a Wikipedia title. The description adds no clarification or mapping between the parameters and the tool's function, so it provides zero value beyond 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 action 'Check whether a Wikipedia title exists,' which is a clear verb+resource, but it is completely inconsistent with the input schema that has no title parameter and instead includes unrelated fields like ref, url, city, etc. This mismatch undermines clarity and makes the purpose ambiguous in practice.

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?

There is no guidance on when to use this tool versus any sibling. The description only gives a bare action with no context, prerequisites, or exclusions, leaving an agent to guess whether this is the right 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.