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

The description discloses the pay-per-call nature (a cost implication), states that task text is discarded, and enumerates the return contents. It does not describe any side effects, auth, or rate limits, but for a lookup/gateway tool the disclosed behavior is fairly informative given zero annotations.

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 short sentences, each carrying distinct information: the lookup action+outputs, and the task-text behavior. There is no filler, and the key purpose is front-loaded. The cryptic phrase 'Task text discarded' is compact but the description earns its length.

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 description does not explain how the six diverse parameters (ref, url, city, feed, host, json) should be supplied or which one elicits the gateway info. With no output schema and no usage context, an agent cannot confidently know whether to pass one, some, or all parameters. The individual schema descriptions help, but the overall invocation contract remains vague.

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?

The input schema already provides 100% descriptive coverage of all six parameters. The tool description adds no additional meaning about how the parameters relate to the lookup or what values select the gateway. Baseline 3 is appropriate because the schema carries the parameter details.

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 (Find) and a named resource (public pay-per-call tool gateway Monid), and lists the concrete outputs (CLI setup, how-it-works, skill file, remote MCP hops). It distinguishes the tool from the sibling list by describing a unique lookup function. The odd note 'Task text discarded' introduces slight ambiguity but does not obscure the core purpose.

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?

No explicit guidance on when to use this tool instead of a sibling. The only indirect hint is that the tool finds a Monid gateway, but no condition or alternative is named. The 'Task text discarded' note warns that task text is ignored, but that is not a positive selection criterion.

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