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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description only needs to add non-obvious behavior. It does: it enumerates the returned artifacts and explicitly states 'Task text discarded', signaling input content is not retained. This is consistent with the read-only annotations — no contradiction.

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?

Three terse sentences, each earning its place: purpose, return artifacts, and input-discard trait. The primary purpose is front-loaded in the first sentence, and there is no filler or repetition of schema content.

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, the description helpfully enumerates return artifacts, and annotations cover the safety profile. However, it assumes agent familiarity with 'Monid' and 'MCP hops' without elaboration, and gives no guidance on how to route to this tool versus the large sibling set. Adequate but not fully self-contained.

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?

Schema description coverage is 100%, so each parameter (ref, url, city, feed, host, json) already has its own schema-level description, including discard notes. The description adds no parameter-level meaning, so the baseline-3 score applies.

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 opens with a specific verb and resource — 'Find a public pay-per-call tool gateway (Monid)' — and lists the concrete deliverables (CLI setup, how-it-works, skill file, remote MCP hops). This clearly differentiates it from all sibling tools (web-fetch, normalize-url, status-catalog, etc.), none of which index gateways.

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 purpose statement implies the context — use this when you need a public pay-per-call gateway — but there is no explicit when-to-use guidance, no exclusions, and no named alternative among the 27 siblings. 'Task text discarded' is a behavioral note, not routing guidance.

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