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

The description and parameter comments disclose that some inputs are discarded after checks, but there is no explanation of side effects, external calls, costs, or other behavioral implications. No annotations are provided to fill this gap.

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 and not padded, but it is dense and ambiguous. The structure is acceptable, yet the phrasing sacrifices clarity for brevity.

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 required parameters, no output schema, and no explanation of invocation context or expected result, the tool is severely under-specified for an agent to use reliably.

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 descriptions cover 100% of parameters, but they are generic or cryptic (e.g., 'HTTPS URL to normalize or cite', 'city name for a public weather hint; discarded after the call'). They do not explain how parameters relate to the tool's main purpose.

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?

Description states a broad purpose ('find a public pay-per-call tool gateway') but the meaning is vague and the parameter list does not clearly map to how the tool would accomplish this. 'Returns connection methods' adds only marginal clarity.

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 use this tool versus any of the many sibling tools. There is no mention of conditions, alternatives, or selection criteria.

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