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

With no annotations, the description must communicate behavioral traits. It only states that the title is discarded, implying no persistence, but it does not disclose whether the tool performs a network request, its read-only nature, failure modes, or any side effects. The coverage is minimal.

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, consisting of two short sentences without any redundant information. It is well-structured and easy to parse, achieving high clarity in minimal words.

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?

The tool description falls short of contextual completeness. It does not explain how to use the nine parameters, which are all optional, nor does it describe the output or behavior. There is no information about expected input format, error conditions, or how this tool fits into the broader toolset.

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 purpose to any specific parameter. The schema contains generic parameters like 'ref', 'url', 'city', etc., with unrelated descriptions, and no explanation of which parameter should hold the Wikipedia title. The tool description adds no semantic clarity to the inputs.

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 action ('Check whether a Wikipedia title exists') and mentions that the title is discarded after the call. However, it fails to specify which of the nine schema parameters corresponds to the title, leaving a gap between the stated purpose and the actual input structure.

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?

The description provides no guidance on when to use this tool versus sibling tools like 'browser-url-ok' or 'fetch-status'. It does not mention any conditions, alternatives, or selection criteria, leaving the agent without usage context.

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