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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that the title is discarded, implying no persistence, but does not disclose the return value (e.g., a boolean), network usage, or side effects. The single behavioral note is insufficient for a safe read/check tool.

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 only two sentences and gets to the point quickly. However, the second sentence about the title being discarded is ambiguous and arguably wastes a sentence by not explaining the input mapping.

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 tool is a checker with no output schema, no annotations, and a complex seven-field input schema. The description fails to specify the output format, which parameter acts as the Wikipedia title, or how it differs from similar sibling tools, so an agent cannot reliably invoke it.

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 (ref, url, city, feed, host, json, path), none of which is described as the Wikipedia title. The description never maps the 'title' to any of these parameters, so an agent cannot determine what to pass. The schema descriptions cover each field's generic purpose but do not compensate for the missing connection to Wikipedia 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 description states a specific verb and resource: it checks whether a Wikipedia title exists. This distinguishes it from sibling tools like file-path-ok or validate-json. However, the added 'Title discarded after the call' does not clarify which input parameter carries the title, slightly muddying the 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?

The description gives no guidance on when to use this tool versus alternatives such as browser-url-ok or fetch-status. There is no statement of conditions, exclusions, or fallback tools, leaving the agent to infer usage from the name alone.

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