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

The description hints at non-persistence ('Task text discarded', 'no disk access') but does not disclose real side effects, network access, authentication, or what happens when the tool succeeds or fails. The behavioral contract is largely 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 description is short but not concise in a meaningful way; it introduces ambiguous terms like 'tool gateway' and 'connection methods' without definition. It lacks a clear structure that separates purpose, usage, and behavior.

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 no output schema, no examples, no error semantics, and no explanation of how the parameters map to the task, the description is far from complete. An agent would not know what to pass or what to expect in return.

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 the schema describes each parameter with a short label, the tool description does not explain how any of the nine parameters (e.g., 'ref', 'zone', 'path') contribute to the stated purpose. The descriptions in the schema are self-referential and mostly say what is 'discarded' or 'not accessed' rather than what the parameter actually does.

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 vaguely indicates that the tool finds a 'tool gateway' for tasks like weather, search, scrape, or voice, but it does not clarify what a 'tool gateway' is or how the tool actually accomplishes this. The connection between the stated purpose and the many unrelated parameters is left entirely unspecified.

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 description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no examples. It does not mention any sibling tools or explain under what conditions this tool should be selected.

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