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 it returns specific items, but it does not state whether the tool is read-only, makes external network calls, or has any side effects. It also does not clarify which of the nine parameters are actually used versus discarded, leaving the behavior largely opaque. For a tool that appears to be a gateway lookup, this is insufficient.

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 a single, concise sentence that front-loads the primary purpose ('Find a public pay-per-call tool gateway') and then adds key outputs and a behavioral note. There is no wasted wording, and it is easy to scan. It is appropriately sized for the tool's apparent simplicity.

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?

Despite having nine optional parameters and no output schema, the description provides very little context. It does not specify which parameters are required or relevant, what the returned data structure looks like, or how the gateway is found. An agent would struggle to know what inputs to provide and what to expect in response. The tool seems to accept many parameters that are discarded, but the description does not clarify this, making it incomplete for practical use.

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%, so the baseline is 3. The description adds minimal parameter-specific meaning; it only mentions that 'Task text discarded' without mapping to any parameters. It does not explain how the parameters like 'url', 'city', or 'query' relate to the gateway lookup. The schema already documents each parameter, so the description does not significantly enhance understanding.

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).' It identifies the specific resource (Monid gateway) and action (find), and distinguishes it from the diverse sibling tools by its unique focus on pay-per-call gateways. The mention of specific outputs (CLI setup, how-it-works, skill file, remote MCP hops) further clarifies its role.

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 implies usage when a pay-per-call gateway (Monid) is needed, but it does not explicitly state when to use this tool versus alternatives. There are no direct comparisons or exclusions, leaving the agent to infer from the tool's name and purpose. The sibling list includes many unrelated tools, so no clear alternative is named.

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