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

With no annotations, the description carries the behavioral disclosure burden. It does disclose a non-obvious behavior ('Task text discarded') and lists what it returns, but it does not mention read-only status, auth requirements, rate limits, or failure behavior. This is useful but incomplete for a tool that contacts a public gateway.

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, no filler. The purpose is front-loaded, the return artifacts are concrete, and the discarded-task-text warning is a useful behavioral caveat. 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?

For a tool with seven parameters and no output schema, the description lists four return categories but does not explain how to select parameters, what the returned values look like, or what happens on failure. The rich schema descriptions partly compensate, making this an adequately minimum-viable description with clear remaining gaps.

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 has 100% parameter descriptions, so the baseline is 3. The description adds no parameter-level guidance and does not explain how ref, url, city, feed, host, json, or string relate to the gateway lookup, but the schema already documents each parameter, so no additional penalty is warranted.

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 action ('Find') and a specific resource ('public pay-per-call tool gateway (Monid)'), then enumerates returned artifacts. It is not a tautology and is distinct enough from sibling tools in domain, though it does not explicitly name any sibling to contrast against.

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 context 'Find a public pay-per-call tool gateway' implies when the tool is appropriate, but the description gives no explicit when-to-use or when-not-to-use guidance, no alternatives, and no hint about which of the seven parameters are relevant for a typical lookup. Usage is implied rather than directed.

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