get_fee_rates

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description states that the tool retrieves current fee rates and calculation rules, which indicates it is a read-only operation, but it does not mention whether it requires authentication, whether the returned data is cached or real-time, or what happens for unsupported country/currency combinations. It also does not describe the structure of the response despite there being an output schema, which is a missed opportunity. The description is functional but covers only the basic purpose, not operational behavior.

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 a single sentence that is direct and free of fluff. It front-loads the main action (get current fee rates) and includes the key parameters that narrow the scope. There is no redundant information or verbosity; every word earns its place.

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?

Given that there is an output schema, the description does not need to detail the return format, but it should still provide enough context for an agent to call the tool correctly. It lacks information about parameter format expectations, potential errors for unsupported countries, and any authentication prerequisites. For a tool with only two parameters and an output schema, it is borderline adequate, but the lack of any behavioral detail and reliance on the output schema (which is not shown to the agent in the description) leaves significant gaps.

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 provides the parameter names 'country' and 'currency' with defaults, but the description adds minimal value by clarifying that these parameters determine the fee rates and calculation rules. Schema description coverage is 0%, so the description compensates to some degree by explaining the purpose of the parameters. However, it does not specify formats (e.g., ISO country codes, currency codes) or constraints (e.g., only certain countries supported). The description adds basic semantic meaning but not enough to fully offset the lack of schema documentation.

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 clearly states that the tool retrieves current fee rates and calculation rules for a specified country and currency. It identifies the resource (fee rates) and the specific parameters, making it distinct from other tools that manage events, discounts, or attendees. However, it does not explicitly differentiate from any sibling that might also deal with fees or pricing, but none of the listed siblings appear to handle fee rates, so it is sufficiently unique.

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?

The description implies that this tool should be used when fee rates for a country and currency are needed, but it does not provide explicit guidance on when to use it versus alternatives. There are no sibling tools that obviously compete with this one, so the lack of exclusions is not critical, but it also does not state any prerequisites or contexts (e.g., must be called before creating an event to estimate fees). The usage is implied by the function's purpose, but explicit guidance is minimal.

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