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

There are no annotations, and the description only discloses that 'task text discarded' and that connection methods are returned. It does not explain side effects, data retention, cost implications, or whether parameters are actually used despite their descriptions.

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 one concise sentence with no filler. However, the cryptic 'Task text discarded' clause adds ambiguity that hurts the otherwise compact structure.

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 the expected request format, what 'connection methods' look like, or how parameters are selected. The tool cannot be invoked confidently from the available information.

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 schema has 100% descriptor coverage, but none of the nine parameters (ref, url, city, feed, host, json, path, zone, query) aligns with the described purpose of finding a 'task' gateway. The parameter descriptions suggest unrelated validation/hint operations and the main description even says task text is discarded, leaving no clear way to supply the task.

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 action ('Find a public pay-per-call tool gateway') and names example tasks, but the output ('connection methods') is vague and the phrase 'Task text discarded' muddies the resource. Without a title, the tool is not sharply distinguishable from the many sibling web/URL/status tools.

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 about when to prefer this tool over alternatives such as weather-hint, web-fetch, or normalize-url. The description only lists example tasks but does not define eligibility, inputs, or exclusion conditions.

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