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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions 'Task text discarded,' which is vague and doesn't explain how the parameters are treated (though the schema hints they are discarded after checks). It doesn't disclose whether the tool makes network calls, requires authentication, or has side effects. The description is insufficient for a tool with 9 parameters.

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 concise – three short sentences that front-load the purpose and mention the key output. No wasted words. However, it is terse to the point of omitting essential usage context, but for conciseness itself, it's well-structured.

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?

For a tool with 9 optional parameters, no output schema, and no usage guidance, the description is incomplete. It doesn't explain how to provide parameters, what the output format looks like, or when to use this tool. Given the complexity and the sibling set, more context is needed.

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 (e.g., 'discarded after the shape check'). The tool description itself adds no parameter information, so it relies on the schema. Since coverage is high, the baseline is 3, and the description doesn't compensate with any additional meaning.

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 clearly states the tool's purpose: '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 is a specific verb+resource and distinguishes it from siblings that deal with URL checks, calculations, or citations. However, it does not explain how the parameters relate to the purpose, which slightly reduces clarity.

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. No mention of conditions, exclusions, or references to sibling tools. An agent has no idea when to pick this over, say, fetch-status or web-fetch.

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