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

The only behavioral note is 'Title discarded after the call,' which hints at statelessness but is vague and does not clarify whether the tool makes network requests, returns a boolean, or has other side effects. With no annotations, the description carries the full transparency burden and falls short.

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 short and front-loaded, but the second sentence 'Title discarded after the call' is confusing and does not clarify the tool's behavior. It is concise but at the cost of essential information.

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 and schema together do not provide enough context to invoke the tool correctly. There is no output schema, no mention of return values or error behavior, and no explanation of which parameter, if any, should be used for the title.

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 schema descriptions are entirely mismatched with the tool's stated purpose. None of the parameters (ref, url, city, feed, host, json, path, zone, query) corresponds to a Wikipedia title, and the inline descriptions reference unrelated concepts like Git refs, URLs, weather hints, and JSON validation.

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'), but it does not identify any input parameter that carries the title. The schema contains nine unrelated properties, so an agent cannot determine how to specify the title.

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 on when to use this tool versus alternatives such as fetch-status, normalize-url, or search-query-len. The intended use case is implied by the name and description, but not explicitly contrasted with sibling tools.

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