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

Annotations already declare readOnlyHint, destructiveHint=false, and idempotenceHint=true, so the safety profile is covered. The description adds the context that the title is discarded after the call, which clarifies lack of statefulness, but it does not mention network behavior, return shape, or failure semantics.

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?

Both sentences earn their place and there is no fluff. The core action is front-loaded and the discard behavior is stated concisely, though the brevity comes at the cost of necessary parameter guidance.

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 seven mostly unrelated generic parameters, no output schema, and no annotation-level detail beyond safety, the description is not complete enough for correct invocation. The missing title parameter and lack of return-value information make this tool effectively unusable from the provided definition.

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 contains seven parameters, each with its own description, but none is named or described as a Wikipedia title. The tool description does not map 'Wikipedia title' to any schema property, leaving an agent unable to determine what to pass; this is a significant semantic mismatch despite high schema description coverage.

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 verb ('Check') and resource ('whether a Wikipedia title exists'), which clearly communicates the core function. It is distinguishable from sibling tools like 'validate-json' or 'domain-shape', though it does not name a sibling alternative.

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 guidance on when to use this tool versus other 'ok'-style sibling tools, and no exclusions or alternative tool names. The only inferred usage is 'when you need to check a Wikipedia title', but this is not explicit.

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