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

No annotations are provided, so the description must carry full behavioral disclosure. It only states 'Title discarded after the call,' which is nonsensical without identifying the title parameter. It does not mention side effects, permissions, return values, or error behavior. This is critically insufficient.

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, which is concise but under-specified. It omits essential operational details and does not front-load any actionable information. This is not conciseness but under-specification.

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?

With 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain how to use any parameter, what the tool returns, or any error conditions. The tool appears to be a shape-checker based on sibling names, yet the description claims Wikipedia title verification, adding to the incompleteness.

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?

Despite 100% schema coverage, the description adds zero semantic value to any parameter. It does not map any parameter to the 'title' concept, and the schema descriptions themselves (e.g., 'Git ref name', 'City name') appear unrelated to Wikipedia titles. The description fails to compensate for the schema's lack of alignment with the stated purpose.

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 verb+resource: 'check whether a Wikipedia title exists.' However, it does not indicate which of the 9 parameters corresponds to the title, making the purpose disconnected from the actual inputs. The phrase 'Title discarded after the call' is ambiguous and adds confusion rather than 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?

There is no guidance on when to use this tool versus siblings like 'browser-url-ok' or 'file-path-ok.' No mention of prerequisites, alternatives, or contextual cues. The agent is left to infer entirely.

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