fetch_trading_fees

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

With no annotations, the description carries the burden and does add real context: it flags that credentials are required, explains that a NEGATIVE maker rate is a rebate paid to the maker, and warns that `volume_30d_estimated: true` means the 30-day volume may undercount. It omits caching/rate-limit behavior and whether the schedule is account-scoped only, keeping it short of a 5.

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?

It is a single dense sentence, but the purpose and the two most valuable caveats (negative maker rate, estimated volume) are front-loaded and each clause earns its place. Slight run-on length is the only cost.

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 output schema and no annotations, the description does the work of describing the return fields and the auth requirement, which is what an agent needs. The dangling `schedule` reference and lack of any mention of refresh cadence keep it from being fully self-contained.

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?

Zero input parameters means the baseline is 4, and the description usefully explains the meaning of a returned field (`volume_30d_estimated`) and a negative maker rate. However, it references a `schedule` scope parameter that does not exist in the empty input schema, which is a mild inconsistency for an agent trying to construct a call.

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 gives a specific verb+resource ("Get the authenticated account's effective fee schedule") and enumerates the content returned: maker/taker bps, fee tier, 30-day volume, and active discounts. It conceptually separates itself from a realized per-fill average, but never names the very similar sibling `get_account_fees`, so an agent must still guess between the two.

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 by the phrase "effective fee schedule ... for the scope named by `schedule`" and the forward-looking-vs-realized clarification. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., per-trade fee data from fills), so the agent is left to infer the selection condition.

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