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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only notes 'Title discarded after the call,' which is a minor detail. It does not explain return values, side effects (e.g., network access), or what 'exists' entails. The behavior is largely opaque, making it difficult to predict tool outcomes.

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 a single sentence, so it is concise without waste. However, it is under-specified for a tool with 9 parameters and no output schema. The brevity is not backed by necessary detail; it reads more as a placeholder than a helpful guide.

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 clearly linked to the stated purpose, and no output schema, the description is woefully incomplete. It fails to explain how to provide the Wikipedia title, what the response looks like, or any constraints. An agent would struggle to call this tool correctly based solely on the provided 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?

Although the schema descriptions cover 100% of parameters, they are generic and unrelated to Wikipedia titles (e.g., 'city', 'zone', 'host'). The description does not identify which parameter represents the title (likely 'query' or 'url'), nor does it add any semantic connection between the parameters and the tool's purpose. The description adds no value in clarifying parameter usage, and the schema descriptions are too generic to compensate.

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+resource, and the tool name reinforces the purpose. However, it doesn't explicitly differentiate from sibling 'shape' tools or mention which parameter supplies the title, though the core intent is unambiguous.

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. It does not mention conditions for use, preconditions, or exclusions. The only hint is the tool name and description, but no explicit 'use this when...' guidance is provided, leaving the agent to infer applicability from the name.

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