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

The only behavioral disclosure is 'Title discarded after the call,' which notes data retention. With no annotations present, the description carries the full burden of explaining side effects, network behavior, and output expectations, but those are missing.

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 text is short and front-loaded, stating the core purpose before the discard note. No words are wasted, though the second sentence introduces a parameter not present in the schema.

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?

There is no output schema and no annotations, yet the tool has seven input parameters. The description does not explain the expected return value, how to pass the title, or when to invoke this tool, leaving the definition far too incomplete for reliable agent use.

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 description's only parameter-related statement references 'title,' but the schema has no title property. The schema's existing parameter descriptions are placeholder-like and unrelated to a Wikipedia title, so an agent still cannot determine which value actually supplies the title.

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 opening sentence clearly states the action and resource: checking whether a Wikipedia title exists. This is specific and not a tautology. However, the description mentions 'title' while the input schema exposes no title property, which slightly undercuts the clarity.

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 usage guidance is provided. The description does not say when to use this tool versus siblings such as web-fetch, citation, or normalize-url, and it gives no context for choosing it over alternatives.

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