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

With no annotations present, the description carries the full burden of behavioral disclosure. It offers one useful behavioral detail—'Title discarded after the call'—and implies a read-only existence check, but it does not explain network behavior, response format, errors, or rate limits, leaving much operational behavior unspecified.

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 appropriately sized at two short sentences, with the core purpose front-loaded and no unnecessary filler. The extra sentence about discarding the title adds behavioral context without redundancy.

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?

This tool has seven parameters, no annotations, and no output schema, yet the description only provides a one-line purpose and a discard note. It fails to specify required fields, which parameter carries the title, what the tool returns, or how the other parameters relate to the operation, making correct invocation impossible to derive.

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 schema describes all seven parameters, but the tool description adds no parameter-level meaning and crucially never identifies which parameter should contain the Wikipedia title. An agent cannot reliably determine how to invoke the tool, despite the schema's high coverage.

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 purpose: checking whether a Wikipedia title exists. It names a specific verb and resource, which distinguishes it from sibling tools like domain-shape or validate-json. However, the input schema contains no obvious `title` parameter, so the stated purpose does not map cleanly onto the actual inputs, which weakens 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 given about when to use this tool versus alternatives such as validate-json or the other shape-checking siblings. The description only states what the tool does, with no mention of conditions, exclusions, or alternative tools.

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