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

No annotations are present, so the description must fully disclose behavior. It only mentions returning connection methods and discarding task text, but does not clarify side effects, network usage, error behavior, or whether it makes external calls.

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 brief and to the point, with a clear structure. The parameter list is flat and easy to scan. No redundant text.

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?

There is no output schema, and the description only vaguely mentions 'connection methods' without specifying the response format. The relationship between the many optional parameters and the task-finding purpose is unexplained, leaving an agent without enough context to invoke the tool effectively.

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 coverage is 100% (all 9 parameters described), but the descriptions are terse and confusingly state that many parameters are 'discarded' after some check. This provides little clarity on how each parameter contributes to the tool's core function, and some descriptions (e.g., 'query' discarded after length check) are misleading.

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 clear verb ('Find') and resource ('public pay-per-call tool gateway'), and lists example tasks (weather, search, scrape, voice). However, the mention that 'Task text discarded' introduces ambiguity about how the task is actually specified or used.

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 provided on when to use this tool versus the many sibling tools (e.g., weather-hint, search-query-len). It does not explain under what circumstances an agent should prefer this router over direct tools.

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