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

No annotations are provided, so the description carries the full burden. It only says 'Title discarded after the call,' implying no persistence, but it does not disclose side effects, error behavior, rate limits, or whether the check is read-only.

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-loaded with the main purpose. However, the second sentence 'Title discarded after the call' is ambiguous and does not earn its place in terms of clarifying behavior.

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?

The description is severely incomplete: it does not explain how to provide the title, what result is returned, what 'exists' means (HTTP status, boolean, etc.), or how the listed parameters relate to the operation. The schema mismatch leaves an agent with no reliable way to invoke this tool.

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 schema description, the descriptions are unrelated to checking a Wikipedia title (e.g., 'Git ref name', 'City name for a public weather hint'). The actual 'title' parameter is missing, so the parameter semantics do not support the stated purpose.

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 input schema contains no 'title' parameter and instead lists unrelated parameters like url, city, and query. This mismatch undermines the clarity of what the tool actually does.

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?

There is no guidance about when to use this tool versus the many sibling tools (e.g., fetch-status, browser-url-ok, search-query-len). No alternatives, prerequisites, or exclusions are mentioned.

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