list_fee_rates

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

With no annotations, the description carries the full burden and does so well: it discloses the HTTP endpoint, that the response is paginated, the required bearer-token authentication, and the 400 error codes. The 'PARAMETERS (all required)' claim conflicts with the schema's two required fields, which slightly undercuts the accuracy of the disclosure.

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?

Clearly front-loaded with purpose then endpoint, parameters, errors and auth, with no filler prose. However, labeling all parameters as required is misleading bulk that a reader must reconcile against the schema.

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 filtered list endpoint with no output schema, it covers the endpoint, pagination, allowed parameter values, error codes and auth requirements. The only material gap is the absence of when-to-use context, and the incorrect 'all required' statement.

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 schema documents 100% of parameters but only with terse labels like 'Plan' and 'Channel'. The description adds real value by enumerating the accepted values for plan, payment_type, channel and item_type and specifying ISO 3166/ISO 4217 formats for country and currency, information absent from the schema.

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?

States a specific verb and resource ('List all available Pricing rates') and names the endpoint, so an agent knows exactly what it retrieves. It does not differentiate itself from the semantically adjacent sibling calculate_item_pricing, so it stops short of a 5.

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 call this versus alternatives such as calculate_item_pricing, nor which filters should be used in which scenario. The agent is left to infer everything about applicability from the parameter list alone.

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