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

With no annotations present, the description carries the full burden of disclosing side effects. It does state that the title is 'discarded after the call,' which is a small privacy/state note, but it never explains whether the check is read-only, whether it contacts Wikipedia, what happens on failure, or what the tool returns.

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 definition is short and front-loaded: the first sentence immediately states the operation. The second sentence about discarding is compact, though it introduces ambiguity by referring to a 'title' that is not present in the schema.

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?

For a tool with seven schema parameters, no annotations, no output schema, and several closely related sibling tools, a 14-word description is far from complete. It does not identify which parameter holds the title, specify the result shape, or differentiate this checker from other 'ok'/shape validation tools.

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 covers 100% of the parameters with individual descriptions, so the baseline would be 3, but the tool description does not map any of those parameters to the stated purpose. None of the seven string fields resembles a Wikipedia title, so the description actually makes the parameter semantics less clear instead of adding useful meaning.

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 opens with a clear verb and object ('Check whether a Wikipedia title exists'), which states an intent. However, the input schema exposes no 'title' parameter – only ref, url, city, feed, host, json, and path – so the stated purpose cannot be mapped to any actual argument, making the definition misleading 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 only a bare statement of function; no guidance is given for when to choose this tool over the many sibling '-ok' and shape-check tools, and no exclusions or prerequisites are mentioned. The phrase 'Check whether a Wikipedia title exists' only implies one use case without equipping the agent to select among alternatives.

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