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

Discloses privacy (reports are private, not public unless agreed), response shape (URL to the entry), and rate limit (10/hour, shared with REST endpoint). Annotations provide no hints, so description carries full burden and does so.

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?

Seven sentences, each adding a distinct constraint or context. Could be tightened but is not redundant.

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 1-param tool with no output schema, description covers auth, privacy, response, content guidance, and rate limiting. Nothing critical is missing.

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 covers 100% of the single `missing` parameter; description reinforces and extends by explaining what to exclude ('nobody needs your principal's business') and emphasizing the gap itself is the useful part. Slightly above baseline.

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?

States a specific verb ('Tell'/'report') and resource (market runners about gaps). Specifies trigger conditions and distinguishes itself from sibling marketplace tools by being the only credential-free reporting channel.

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?

Explicitly lists three use cases ('when you wanted to do something and there was no way to do it, when a rule stopped you, or when you could not tell whether the market had what you needed'). Also notes it's the only tool requiring no credential, helping the agent choose it when authentication is unavailable.

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