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

The description discloses that the title is discarded after the call, but it does not explain which parameter is the title, nor does it mention any other behavior such as network access, rate limits, or side effects. With no annotations, the description carries full burden, and it fails to clarify the parameter mapping, leaving the behavior ambiguous. The mismatch between 'title' and the schema's lack of a title parameter is confusing.

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 very short, which is concise, but it is under-specified. It omits critical information about parameter usage and expected output. The brevity is not effective because it does not convey enough information for an agent to correctly invoke the tool.

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?

Given the tool has 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain how to invoke the tool, what to expect as a result, or which parameter to use. This is inadequate for an agent to use the tool correctly.

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 input schema has 100% description coverage, so each parameter is individually documented. However, the tool description does not add any meaning beyond the schema and fails to connect any parameter to the purpose of checking a Wikipedia title. The description mentions 'title' but none of the 9 parameters is named or described as such, creating a gap that the description does not compensate for.

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 clearly states a specific action and resource: checking whether a Wikipedia title exists. It is distinct from sibling tools that check URLs or other shapes. However, it does not clarify which input parameter carries the title, and it doesn't explicitly differentiate from tools like 'fetch-status' or 'web-fetch' that might also check existence of resources, though the Wikipedia-specific scope helps.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention conditions, exclusions, or alternative tools. There is no context on when to prefer this over other shape-checking tools. The single sentence is purely functional without any usage direction.

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