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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions that the title is discarded, which hints at statelessness, but it does not disclose output format, error behavior, or any side effects. 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 two short sentences with no fluff, achieving conciseness. The purpose is front-loaded, and the note about discarding the title is brief. However, it is too sparse to be fully helpful, but conciseness itself is not penalized heavily.

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 9 parameters, none required, no output schema, and no annotations, this description is grossly incomplete. It does not specify which parameter is the title, what the return value looks like (boolean, status, etc.), or any error conditions. An agent cannot reliably call this tool correctly based on the description alone.

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?

Schema description coverage is 100% (all 9 parameters have descriptions), so the baseline is 3. The description does not add meaning beyond the schema—it fails to identify which parameter represents the Wikipedia title (likely 'query' but not stated). It neither clarifies parameter relationships nor compensates for the schema's generic descriptions.

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 clear action: 'Check whether a Wikipedia title exists.' This is a specific verb and resource, but it does not distinguish from sibling tools or clarify which parameter holds the title. The name reinforces the purpose, yet the schema's many unrelated parameters introduce ambiguity.

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 on when to use this tool versus alternatives like 'browser-url-ok' or 'fetch-status'. There is no mention of exclusions, prerequisites, or context in which this tool is preferred. The description leaves usage entirely to inference.

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