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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that 'Task text discarded' and that it 'Returns connection methods,' but provides no details on side effects, required permissions, error handling, or what the returned connection methods look like. This is insufficient for a tool with no annotation coverage.

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 two sentences and relatively brief, but it is vague and does not efficiently convey the tool's operation. It mentions 'Task text discarded' without explaining what 'task text' refers to, and the sentence structure is not front-loaded with the most critical information for an agent. It is concise but not clearly structured.

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?

The tool has 9 optional parameters, no output schema, and no annotations. The description does not explain how the parameters are used, what the connection methods contain, or how an agent should format a call. The description is grossly incomplete for a tool of this complexity; an agent would likely misuse it without further context.

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 input schema has 100% description coverage, so each parameter is individually documented. The tool description adds no additional meaning beyond the schema—it does not explain how parameters relate to the gateway selection or what each parameter's role is in the task. Baseline 3 applies because the schema handles parameter documentation, but the description fails to provide higher-level context.

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 ('pay-per-call tool gateway'), and lists example tasks. However, it does not differentiate this tool from siblings like weather-hint, search-query-len, or validate-json, which appear to cover specific tasks. The purpose is understandable but not distinct.

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 alternatives. The description mentions task examples but does not explain how to decide between this gateway and the dedicated sibling tools, nor does it state any conditions or exclusions. An agent cannot determine the appropriate context for calling this tool.

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