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

With no annotations present, the description carries full behavioral disclosure duty. It states the core check and that the title is discarded, but it does not disclose how the result is returned, whether a network request is involved, or any error behavior. This is insufficient for a tool with no annotation coverage.

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 and front-loaded, with the main purpose stated first. The second sentence adds one behavioral detail, but the overall definition is under-sized for a seven-parameter tool that still needs invocation guidance.

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?

There are seven parameters, no annotations, and no output schema, yet the description does not explain which parameter is the title, what the return value is, or how the tool should be invoked. This is fundamentally incomplete for an agent to use 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 description refers to a 'title,' but the input schema exposes ref, url, city, feed, host, json, and path, each described as unrelated to Wikipedia titles and mostly 'discarded.' An agent cannot determine which parameter, if any, should hold the Wikipedia title, and the description adds no mapping to 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 clearly states a specific action and resource: 'Check whether a Wikipedia title exists.' This distinguishes the tool from sibling tools like fetch-status or normalize-url. However, it does not explain how the title is passed, and the additional 'Title discarded after the call' clause adds some confusion.

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 alternatives, no prerequisites, and no exclusions. The only usage indication is a near-restatement of the operation: use it to check Wikipedia title existence.

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