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

With no annotations, the description must carry the full behavioral burden. It only discloses that the title is discarded after the call, but does not state whether the tool performs a network request, is read-only, has error handling, or what it returns. The note about discarding is a minor transparency point, but overall behavior is underspecified.

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 extremely concise: two short sentences with no filler. It states the core action and a behavioral note. This is appropriately sized for the information it provides, though the lack of content limits its usefulness.

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?

For a tool with 9 parameters, none required, and no output schema or annotations, the description is grossly incomplete. It does not specify which parameter is the title, what the return value looks like, or any usage context. An agent cannot reliably call this tool based on the description and schema 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?

The description does not map the concept of a 'Wikipedia title' to any of the 9 parameters. The schema provides descriptions for each parameter, but they are generic and unrelated to Wikipedia (e.g., 'City name for a public weather hint'). The description fails to clarify which parameter holds the title, making it impossible for an agent to know how to invoke the tool correctly.

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 the tool's function: 'Check whether a Wikipedia title exists.' This is a specific verb and resource, distinguishing it from generic URL checkers. However, it does not explicitly mention how the title is supplied or differentiate it from sibling tools that might also check URLs or titles, so it lacks full clarity about the intended input.

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 provided on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or related tools, leaving the agent to infer when a Wikipedia title check is appropriate. This is a significant gap given the large sibling list.

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