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

With no annotations, the description carries the full burden. It only discloses that the title is discarded after the call, which is a minor detail. It does not state read-only behavior, side effects, permissions, or limitations, and it is inconsistent with the generic parameters.

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 concise, one sentence, and front-loads the core action. However, it is so brief that it omits essential information like which parameter to use, making it under-specified rather than efficiently concise.

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 nine parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain how to specify the title, what the other parameters are for, what the return value is, or any usage context. An agent cannot reliably call this 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?

Schema coverage is 100% with each parameter having a description, but these descriptions are generic (e.g., 'Git ref name', 'City name') and do not relate to Wikipedia titles. The tool description implies a title parameter but none exists in the schema, so the semantics are confusing and do not add meaningful value.

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'—which distinguishes it from sibling tools like browser-url-ok or file-path-ok. However, it fails to indicate which of the nine parameters carries the title, making the purpose ambiguous despite the verb+resource.

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. It does not mention that it is for Wikipedia title checks specifically, nor does it contrast with sibling tools or state any conditions or exclusions.

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