Get Fee Info

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

The description adds the prerequisite of API keys in the environment, which is useful context. However, with no annotations provided, it does not explicitly confirm read-only behavior or describe the return format, leaving some transparency gaps.

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, concise two-sentence structure that front-loads the primary purpose and includes an important prerequisite. No wasted words.

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 simple no-parameter getter, the description conveys the core purpose and auth requirement. However, it lacks usage guidance and does not specify what 'related fee information' includes, which would be helpful given there is no output schema.

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?

There are no parameters, so the description does not need to explain parameter semantics. The schema is empty, and the baseline for zero parameters is high; no additional parameter information is expected.

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 the tool fetches the caller's trading fee rates and related fee information, using a specific verb and resource. This distinguishes it from sibling tools like get_borrow_rates_info, which are about different financial data.

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 only mentions an environment prerequisite (API keys) but gives no guidance on when to use this tool versus alternatives. It does not state exclusions or specify use cases beyond fetching fee information.

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