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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that task text is discarded and enumerates return contents. However, it does not mention whether the call is read-only, requires anything, or how the parameters affect behavior, so transparency is partial.

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?

Two tight sentences, front-loaded with the core purpose and followed by the key return information and discard warning. Every clause earns its place.

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 lists return artifacts but never explains how to actually invoke the tool: which of the six heterogeneous parameters (ref, url, city, feed, host, json) is required, optional, or even relevant to finding a Monid gateway. With no output schema or usage hints, an agent cannot confidently choose a valid call shape.

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 provides descriptions for all six parameters, so coverage is 100%. The tool description itself adds no parameter-level meaning, which lands at the baseline 3 for fully documented schemas.

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 uses a specific verb ('Find') and names the resource ('public pay-per-call tool gateway (Monid)') and lists the concrete returned artifacts (CLI setup, how-it-works, skill file, remote MCP hops). It does not explicitly contrast with siblings, but the discovery/index nature is clear enough to distinguish it from the URL/status/shape utilities in the sibling list.

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 a clear context: use it when you need to locate a Monid gateway. It does not name alternatives or exclusion criteria, so it does not reach a 5, but the 'find a ... gateway' framing provides a usable selection signal.

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