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

No annotations are present, and the description only says 'Title discarded after the call' even though no title parameter exists. It fails to disclose what the tool actually does with inputs, what it returns, or any side effects.

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 only one sentence and is concise, but the phrase 'Title discarded after the call' introduces confusion rather than clarity. It does not front-load useful information about the actual operation.

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 no output schema, no required parameters, and a schema that does not match the description, the definition is incomplete. An agent cannot infer expected inputs, outputs, or behavior from the provided information.

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 has 100% description coverage, the parameter descriptions are generic and unrelated to checking a Wikipedia title. They do not clarify how any parameter relates to the tool's stated purpose, so the semantics are 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 the tool checks whether a Wikipedia title exists, but the input schema contains no 'title' parameter and instead lists unrelated parameters like 'ref', 'url', and 'city'. This makes the actual purpose confusing and not actionable as described.

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 tool. The description provides no usage context, and the mismatch between the described purpose and the actual schema leaves an agent without clear direction.

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