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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does mention 'Task text discarded' and 'no disk access' for a parameter, but it doesn't disclose network usage (implied by 'remote MCP hops'), side effects, or what happens to other inputs. It's not misleading but far from transparent about the tool's behavior.

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 brief (two sentences) and front-loaded with the main action, but it's so terse that it omits critical information. Conciseness is not a problem; clarity is. The structure is acceptable but the content is insufficient.

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?

Given 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. It doesn't explain how inputs are used, what the output format is, or how to interpret the returned artifacts. An agent would struggle to call this tool correctly without additional context.

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 coverage is 100% (every parameter has a description), so the baseline is 3. The tool description adds no additional meaning beyond what the schema already provides; it doesn't explain how parameters like 'url', 'city', or 'json' relate to the gateway discovery purpose.

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 says 'Find a public pay-per-call tool gateway (Monid)' and lists outputs (CLI setup, how-it-works, skill file, remote MCP hops), but it doesn't clarify what the tool actually does with its 9 heterogeneous inputs. It doesn't differentiate from siblings like browser-url-ok or validate-json; the purpose is vague and the connection between inputs and outputs is missing.

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?

There is no guidance on when to use this tool versus alternatives. The description mentions it's for finding a gateway, but doesn't specify what input triggers it or when an agent should prefer it over other shape-checking or validation tools. No exclusions or prerequisites are given.

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