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

Annotations already declare readOnlyHint, destructiveHint, and idempotenceHint. The description adds a non-obvious data-handling detail—the title is discarded after the call—which is not covered by annotations. However, it omits other behavioral context such as return value or error behavior, and the reference to a 'title' is inconsistent with a schema that has no title parameter.

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 tight—two short sentences with no filler. The core purpose is front-loaded and the discard note is relevant. It sacrifices necessary detail for brevity, but the conciseness itself is effective.

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 ten schema parameters and no output schema, a two-sentence description covering only the Wikipedia-title use case is inadequate. It fails to explain the role of the other parameters, what the output is, or how the tool behaves. The mismatch between the described 'title' and the actual parameter list leaves significant gaps for an agent.

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 descriptions cover each property, but the tool description refers only to a 'Wikipedia title' that maps to none of the schema properties. This mismatch actively confuses parameter binding; an agent cannot tell whether the title is passed via url, ref, or another field. The description adds no clarifying semantic beyond the schema and introduces an ambiguous entity.

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 uses a specific verb ('Check') and resource ('Wikipedia title') and clarifies the operation's effect ('Title discarded after the call'). It does not, however, differentiate this from sibling verification tools such as browser-url-ok or file-path-ok, which also check existence or validity.

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 gives no context for when to choose this tool over alternatives. It neither states when a title-existence check is appropriate nor names any sibling tool for comparison. An agent cannot infer selection criteria beyond the narrow purpose.

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