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

With no annotations, the description carries full responsibility for disclosing behavior. The description claims the tool returns connection methods and finds gateways, but the schema indicates each parameter is discarded after a shape or length check. This misrepresents the actual behavior, which appears to be validation rather than gateway lookup. It also doesn't disclose that inputs are discarded, except through schema hints. The description is misleading and contradictory.

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 one sentence, which is concise in length, but it lacks essential information. It fails to front-load the actual function or clarify the ambiguous purpose. Conciseness should not come at the expense of clarity; here it is under-specified rather than efficiently informative.

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?

For a tool with 9 optional parameters and no output schema, the description is grossly incomplete. It doesn't explain what the tool actually does, what the return format looks like, how parameters relate to the gateway-finding claim, or when it should be used. Without annotations, the description fails to provide any meaningful context. It is inadequate for an agent to understand or correctly invoke the tool.

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%, so the baseline is 3. The schema descriptions are clear about each parameter's purpose (e.g., 'discarded after the shape check'). The top description adds no parameter meaning and even conflicts with the schema's implied validation purpose. Since the schema is adequate, the description doesn't need to add much, but it also doesn't clarify the relationship between parameters and the stated gateway-finding purpose. Thus, a baseline 3 is appropriate.

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 purpose ('Find a public pay-per-call tool gateway') but is vague and confusing. It doesn't specify what 'connection methods' are, and it mentions 'task text discarded' while no task parameter exists. The purpose conflicts with the parameter schema, which suggests validation of individual inputs rather than gateway discovery. It is not a tautology but lacks specificity and fails to differentiate from sibling 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 provided on when to use this tool versus alternatives. It doesn't mention any sibling tools or exclusions. For instance, for weather tasks, weather-hint exists, but the description doesn't clarify when this tool should be preferred. There is no when-not-to-use information.

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