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

There are no annotations and the description only states 'Title discarded after the call'. It does not clarify side effects, network access, read-only behavior, or error handling. The mismatched parameter descriptions further obscure what the tool actually does.

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, but its brevity works against clarity. The parameter descriptions appear to be copy-pasted from other tools and add noise rather than concisely explaining the tool's actual interface.

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 no output schema, no annotations, and a description that does not match the input schema, the tool definition is critically incomplete. An agent cannot reliably determine what parameters to pass or what the tool returns.

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?

Although every parameter has a description, the descriptions are entirely inconsistent with the tool's stated purpose (e.g., 'Git ref name', 'City name', 'IANA timezone name' have no relation to checking a Wikipedia title). The schema does not include a 'title' parameter despite the tool name and description.

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 clear action (check whether a Wikipedia title exists) but the parameter schema contains a mismatched set of unrelated parameters (Git ref, URL, city, feed, host, JSON, path, timezone, search text) with no 'title' field anywhere. This creates significant confusion about the tool's actual purpose.

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 versus the many related sibling tools (browser-url-ok, fetch-status, normalize-url, etc.). The description does not mention alternatives or conditions for selection.

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