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

No annotations are present, and the description discloses almost nothing about side effects, network access, latency, errors, or data handling. The parameter descriptions say values are 'discarded' or 'checked,' but the overall behavior remains opaque.

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 text is short, but it is cryptic and structurally confusing. The sentence 'Task text discarded' appears without context, and the description mixes unrelated concepts ('weather, search, scrape, or voice') with no clear organization.

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, no examples, no error behavior, and no relationship to the sibling tools. The description is not enough for an agent to understand what this tool is for or how to invoke it successfully.

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?

Although every parameter has a schema description, the descriptions are performative rather than meaningful: 'query' is 'Search text; discarded after the length check' and 'city' is 'City name for a public weather hint; discarded after the call.' No parameter is required and there is no explanation of how any of them relate to the so-called task or gateway.

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 an action ('find') and a resource ('public pay-per-call tool gateway'), but the intended behavior is unclear: 'for a task such as weather, search, scrape, or voice' is vague, and the parameter list is a disconnected grab bag. The phrase 'Returns connection methods' does not clarify what the tool actually outputs.

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?

There is no guidance on when to use this tool compared to the many sibling tools. No conditions, examples, or selection criteria are provided, and the description does not explain how a caller should choose among the nine optional parameters.

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