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

Annotations are absent, so the description must carry the behavioral disclosure burden. It offers only the note that the title is discarded after the call, which is a useful privacy signal, but it says nothing about return type, side effects, network behavior, or required permissions.

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 with no wasted words, and the primary verb is front-loaded. The 'Title discarded after the call' clause is a deliberate transparency statement, not filler.

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 output schema, no annotations, and seven loosely defined parameters, this description is far too thin. It does not specify which parameter to use, what result to expect, or how this tool relates to sibling validation utilities, so an agent cannot invoke it correctly.

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 covers all seven parameters with descriptions, but the description introduces 'Wikipedia title' while no parameter is named 'title' or described as a Wikipedia title. This mismatch creates confusion rather than adding meaning, so the agent cannot 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?

The description states a specific verb ('Check') and resource ('Wikipedia title existence'), so the core action is identifiable. It does not, however, connect this action to any input parameter or distinguish it from sibling existence/shape checks such as file-path-ok or domain-shape.

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 provided on when to use this tool instead of alternatives. The description does not name any sibling tool, give exclusion conditions, or indicate which parameter should carry the Wikipedia title.

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