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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose that the title is discarded after the call, which is useful privacy context, but it does not mention whether the operation is read-only, performs a network lookup, or returns any result.

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 very short and front-loads the core purpose. The second sentence about discarding the title is arguably useful privacy information, but the overall terseness leaves important semantic gaps.

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 simple existence check, the description might be sufficient if the title parameter were obvious, but the schema mismatch makes it hard to invoke correctly. There is also no mention of return format or output semantics, despite there being no output schema to fill that gap.

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 lists seven parameters with individual descriptions, but none of them is clearly a Wikipedia title. The description fails to bridge 'title' to any schema property, so an agent cannot determine which argument to supply.

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 action ('check whether a Wikipedia title exists') on a specific resource, which clearly defines what the tool does. It is distinct from sibling tools such as file-path-ok or validate-json, even without naming alternatives.

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 implies a use case: verifying a Wikipedia title's existence. However, it gives no explicit guidance on when to prefer this tool over alternatives, no exclusions, and no context about prerequisites or expected inputs.

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