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

With no annotations, the description carries the full behavioral burden. It discloses only that the title is discarded after the call, but does not mention what the call returns, whether it performs a network request, or why the input schema has no title-like parameter. This omission creates confusion about the tool's actual behavior.

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 has no filler, but the brevity crosses into under-specification: it introduces a 'title' concept that the schema never names. Efficiency does not compensate for the missing parameter mapping.

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 no annotations and no output schema, the description should name the required input and explain the return value or result semantics. It does neither, and the mismatch between the description and the schema makes correct invocation unreliable.

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 input schema has six parameters with individual descriptions, but none corresponds to a 'title', which is the tool's core concept. The description adds no parameter-level guidance and actually conflicts with the schema, leaving an agent unable to determine which parameter to populate.

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?

States a specific verb ('Check') and resource ('Wikipedia title exists'), which is clear on its own. However, it does not distinguish from sibling validation/shape tools like domain-shape or browser-url-ok, and the key 'title' resource does not appear in the input schema.

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 on when to use this tool versus alternatives such as normalize-url, validate-json, or domain-shape. The only usage signal is the name, and the description offers no exclusions or conditions.

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