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

With no annotations, the description carries the full burden. It discloses that 'Task text discarded' and that parameters are 'discarded after the check' per the schema, indicating a stateless, non-retained behavior. However, it doesn't mention auth needs, rate limits, or whether it performs any side effects. The 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 sentences with zero waste. The purpose is front-loaded, and the note about discarding task text is important and placed at the end. 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?

With 9 parameters, none required, and no output schema, the description is too thin. It lists returned items but doesn't explain how inputs map to the search, what parameters are needed, or what the actual return format looks like. An agent would be unsure what to pass to get the gateway information. The description leaves too much to inference.

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 schema already explains each parameter's type and purpose. The description adds that 'Task text discarded' and that some parameters are discarded after checks, which hints at a validation-only role. But it doesn't explain how these parameters relate to the gateway lookup or which ones matter, so it adds marginal value over the schema.

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: 'Find a public pay-per-call tool gateway (Monid)' and lists what it returns (CLI setup, how-it-works, skill file, remote MCP hops). This clearly distinguishes it from the sibling tools, which are all different focused tools (browser checks, formatting, etc.).

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. It doesn't mention any context where this is preferred, nor does it name any related gateway-lookup tools. An agent must infer its purpose from the name and description alone.

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