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

Annotations already declare readOnly=true and destructive=false. The description adds the note 'Title discarded after the call,' giving extra context about resource lifetime. This is useful but modest; it does not reveal return behavior or error conditions, and the annotation profile already covers the main safety attributes.

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?

Two short sentences, front-loaded with the primary purpose and immediately followed by the resource-disposal note. Every word earns its place with no redundancy or filler.

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?

The description omits the essential mapping between the tool's purpose and its input schema. With no output schema and multiple unrelated-looking parameters, an agent cannot reliably construct a valid call. The discard note is the only behavioral detail, and no return value or error semantics are described.

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 does not explain which of the seven schema parameters corresponds to the Wikipedia title. The schema properties (ref, url, city, feed, host, json, path) have generic 'discarded after the shape check' descriptions that appear unrelated to Wikipedia titles. There is a critical mismatch between the tool's stated purpose and its input contract, leaving an agent unable to determine what to pass.

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 verb and resource: 'Check whether a Wikipedia title exists.' This clearly conveys what the tool does. It does not explicitly distinguish it from sibling tools like browser-url-ok or github-repo-shape, so it falls one point short of top marks.

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. The description does not mention prerequisites, exclusions, or related sibling tools. An agent must infer entirely from the tool name and task context when this should be invoked.

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