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

No annotations are provided, so the description bears the transparency burden. It does disclose a useful behavioral trait: 'Title discarded after the call,' which implies a read-only, non-retaining operation. However, it does not describe the response meaning, possible side effects, network behavior, or error cases, so the disclosure is incomplete.

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 no filler words. Both sentences carry information. However, the brevity masks severe under-specification, and the discard statement does not repair the missing mapping between the purpose and 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?

Given seven schema properties, no output schema, no annotations, and a description that references a title parameter which doesn't appear in the schema, an agent has almost no chance to call the tool correctly. The description does not define any meaningful return contract or usage conditions and is therefore inadequate.

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 never explains which parameter holds the Wikipedia title, and in fact the schema has no 'title' property at all. The provided parameters (ref, url, city, feed, host, json, path) are described in the schema but appear irrelevant to the stated purpose, so an agent cannot determine what input to supply. This is a critical semantic gap.

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 and resource: 'Check whether a Wikipedia title exists.' That is a clear purpose and it is distinguishable from sibling shape-checkers by name and a plain-language, but the lack of any connection to the actual input schema introduces ambiguity about how the title is supplied.

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?

No guidance is given about when to use this tool instead of sibling tools such as web-fetch, normalize-url, or the many shape-checkers. The intended context is only implied by the name and the word 'Wikipedia'; there are no prerequisites, exclusion, or alternative routing instructions.

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