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

No annotations are provided, so the description must fully disclose behavior. It states that task text is discarded and that parameters are used only for shape checks, which is a form of transparency. However, it does not explain how the tool determines the task from the presence of specific parameters (e.g., city implies weather), nor does it describe side effects, authentication, or rate limits. The return format of 'connection methods' is also left vague. This is a significant gap for a meta-tool with 9 optional parameters.

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 only two sentences and stays on topic. It front-loads the core purpose and the output type. It could be more explicit about parameter-to-task mapping, but there is no fluff or irrelevant detail, so it earns a 4 for conciseness and 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 9 optional parameters, no output schema, and a non-trivial purpose (finding a gateway), the description is too thin. It does not explain how parameters select a task category, what 'connection methods' look like (e.g., URLs, credentials, formats), or any preconditions. An agent would struggle to use this correctly without additional inference. The description leaves critical context uncovered.

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% and each parameter has a description that notes it is discarded after a check (e.g., 'Git ref name; discarded after the shape check'). The tool description adds little beyond this, only repeating that task text is discarded. Since the schema already documents each parameter's purpose and fate, the description meets the baseline for parameter semantics without adding extra meaning.

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 a resource (a public pay-per-call tool gateway), and lists example task categories (weather, search, scrape, voice). It is clear enough to distinguish from siblings like weather-hint or search-query-len, though it doesn't explicitly name alternatives. The phrase 'Task text discarded' adds a minor ambiguity about what input actually drives the lookup.

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 versus the many sibling tools. It does not say 'If you need weather data, use weather-hint; if you need a gateway for weather, use this.' The description implies it returns connection methods rather than performing the task, but it never explicitly contrasts with the specific sibling tools, leaving the agent to infer the usage boundary.

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