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

With no annotations, the description carries the behavioral disclosure burden. It adds a useful privacy note ('Task text discarded') and lists returned artifact classes, but it leaves operational traits unstated, such as whether calls incur charges, require auth, or involve network requests.

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 short sentences carry the core purpose, return contents, and discard policy with no filler. The purpose is front-loaded and every sentence 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 tool has no output schema, no annotations, and 9 optional parameters, yet the description doesn't explain invocation shape, which parameters to actually use, or what the returned artifacts look like. The cost/auth implications of 'pay-per-call' are also left ambiguous, so an agent would struggle to call it correctly.

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 the baseline is 3. The schema already documents all 9 parameters, but the description adds no guidance on which parameter to pass or why inputs are 'discarded after the shape check.'

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 names a specific verb and resource ('Find a public pay-per-call tool gateway (Monid)') and enumerates concrete return artifacts: CLI setup, how-it-works, skill file, and remote MCP hops. This clearly distinguishes it from the sibling shape-checkers and hints.

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 makes the intended scenario clear—looking up the Monid pay-per-call gateway—and lists what the caller will receive. However, it never contrasts this tool with sibling alternatives or states when NOT to use it.

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