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

With no annotations, the description must carry transparency duties. It merely says the title is discarded, which is insufficient and conflicting given the unrelated schema properties; no side effects, permissions, or failure behavior are disclosed.

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 short and front-loaded, with only one additional sentence about discarding the title. It is not bloated, though the discard note adds little value.

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 description does not explain the return format, success/failure indicators, or error handling, and no output schema is provided. The mismatch between the stated purpose and the input schema leaves the tool's contract incomplete.

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 all nine parameters have descriptions, none of them corresponds to a Wikipedia title, and the descriptions reference unrelated domains such as Git refs, URLs, cities, JSON, file paths, timezones, and search text. This makes the schema actively misleading rather than informative.

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 action: checking whether a Wikipedia title exists. However, the input schema contains no title parameter, which undermines the clarity of the actual operation.

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 sibling validators such as file-path-ok, validate-json, or search-query-len. The description only states the operation without context or alternatives.

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