Trading fees

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful content detail (maker/taker, percent, 30-day volume tiers) but does not state whether results are public/global or personalized to the caller, nor how often the schedule changes.

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?

A single front-loaded sentence that names the resource first and then enumerates the returned fields. No filler, no repetition of the title or annotations.

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 no parameters, no output schema and annotations covering the safety profile, the description's job is to convey what comes back, which it does. It could be marginally stronger by noting that the schedule is a global reference rather than account-specific.

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 tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no filtering input is required to obtain the full schedule.

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?

Names a specific resource (the trading fee schedule) and its exact contents: maker/taker rates in percent, keyed by 30-day USD volume tier. It is readily distinguished from siblings like get_ticker, get_orderbook and get_candles. The only shortfall is the absence of an explicit verb (get/list), which the title partially supplies.

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?

Usage is only implied: the resource itself makes clear this is the lookup for the exchange's fee tiers, and no overlapping sibling offers the same data. There is no explicit when-to-use statement, no mention of prerequisites, and no guidance on whether the schedule is account-specific or global.

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