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

There are no annotations, so the description carries the disclosure burden. It does disclose a notable behavior ('Task text discarded') and the 'Find/Returns' framing suggests a read-only lookup. However, it is silent on side effects, external calls, or cost implications of a 'pay-per-call' 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?

Three short sentences deliver the purpose, the deliverables, and a behavioral caution with no filler. The core action is front-loaded in the first sentence.

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 tell an agent how to form a call: six heterogeneous parameters are present, but there is no indication of which to supply, whether any are required, or how they map to finding Monid. With no output schema and no required-field information, important invocation context 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?

The input schema already describes all six parameters with 100% coverage, including their 'discarded after' behavior. The description adds no parameter-level meaning beyond the standalone statement that task text is discarded, which is not tied to any specific parameter.

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 names a specific operation and resource: 'Find a public pay-per-call tool gateway (Monid)' and lists concrete deliverables (CLI setup, how-it-works, skill file, remote MCP hops). It is not a tautology and does not resemble any of the sibling tools, though 'Monid' is unexplained and the connection to the six input parameters is unclear.

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 intended use is implied: invoke this tool when you need Monid's CLI setup, how-it-works, skill file, or remote MCP hops. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned.

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