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

With no annotations, the description must disclose behavioral traits. It only states 'Title discarded after the call,' which hints at statelessness but does not explain side effects, permissions, or return values. The description is too sparse to convey the tool's actual behavior, and the mention of 'Title' conflicts with the schema's parameter set.

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—which is good for front-loading. However, it is under-specified and does not structure information in a way that helps the agent. It is short but lacks essential context, so it is not appropriately informative.

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 nine optional parameters and no output schema, this description is severely incomplete. It does not explain the relationship between the parameters and the claimed function, nor does it provide any usage context or expected behavior. An agent cannot reliably invoke this tool based on the given information.

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 adds no meaning to any of the nine parameters. Although the schema provides descriptions for each parameter (100% coverage), these descriptions are unrelated to Wikipedia titles (e.g., 'Git ref name', 'City name'). The description fails to explain how parameters like 'url' or 'query' relate to the tool's stated purpose, leaving the agent without usable guidance.

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 purpose: 'Check whether a Wikipedia title exists.' This is specific and action-oriented. However, it does not differentiate from sibling tools like 'domain-shape' or 'file-path-ok', and more importantly, the input schema contains no 'title' parameter, making the intended usage ambiguous. The mismatch between the description and schema undermines clarity.

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. An agent has no basis for selecting this over similar check tools.

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