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

With no annotations provided, the description carries the full burden. It mentions 'Title discarded after the call,' implying a stateless, read-only check, but it does not disclose the result format, error behavior, or any side effects. This minimal disclosure is insufficient for a tool with no annotations.

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 brief, consisting of two sentences with no redundancy. However, this brevity borders on under-specification; it omits critical invocation details. It is concise but not effectively structured for agent comprehension.

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 optional parameters, no output schema, and no annotations, this description is grossly incomplete. The agent has no idea which parameter to use, what the return value represents, or how to interpret success/failure. The description fails to provide the necessary context for correct invocation.

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 schema coverage is 100%, the parameter descriptions are generic and mismatched (e.g., 'query' is 'Search text' and 'path' is 'File path to check'), with no indication of which parameter holds the Wikipedia title. The description adds no clarity about parameter usage, so it fails to compensate for the schema's irrelevance.

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 specific verb and resource: 'Check whether a Wikipedia title exists.' This clearly distinguishes it from sibling tools that handle URLs, domains, or other entities. However, it does not explicitly differentiate from potential overlapping tools or name alternatives, so it falls short of a 5.

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 siblings, nor any mention of prerequisites or context. The description provides no exclusions or alternative routing, leaving the agent to infer usage from the name alone.

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