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

No annotations are provided, so the description carries the behavioral disclosure burden. It adds useful context: the tool appears read-only in spirit, it is pay-per-call, and task text is discarded. However, it does not disclose auth needs, whether remote MCP hops are invoked, or failure behavior, leaving significant gaps.

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 short, front-loaded, and contains no filler; the first sentence identifies the purpose and the second adds return contents and a privacy-relevant discard note. It is slightly too terse to earn a 5 because 'Monid' and the input-output mapping remain unexplained.

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?

With nine optional parameters and no output schema, the description does not explain which parameters to provide, how they influence the returned artifacts, or what the CLI setup and remote MCP hops actually look like. The per-parameter schema helps, but the overall call pattern is ambiguous.

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 description coverage is 100%, so the schema already documents all nine optional parameters. The tool description itself adds no parameter-specific meaning beyond the general note that task text is discarded, so the baseline 3 is appropriate.

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 target ('public pay-per-call tool gateway (Monid)'), and lists concrete returned artifacts (CLI setup, how-it-works, skill file, remote MCP hops). This distinguishes it from the sibling check/hint tools, though 'Monid' and the relationship between inputs and outputs are unexplained, so it is not a 5.

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 guidance is given on when to use this tool versus its many siblings, such as web-fetch, normalize-url, or validate-json. The description does not state preferred scenarios, prerequisites, or exclusions; it only warns that task text is discarded.

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