bitpin_get_commissions

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

With no annotations at all, the description carries the full disclosure burden and delivers the two operationally critical facts: authentication is required and there is a 1000/day rate limit. It stops short of describing the response shape (e.g., whether rates are nested per market or flat) or error behavior, which matters given there is no output schema.

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?

Three short sentences with zero filler, ordered by importance: what it returns, then the auth requirement, then the rate limit. Every sentence 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?

For a no-argument read tool with no output schema, the description covers purpose, scope, auth, and throttling — nearly everything needed to call it correctly. The only mild gap is the response structure, which an agent could reasonably guess but is not told.

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 there is nothing for the description to disambiguate; baseline applies. The schema is empty and complete, and the 'all markets' phrasing correctly signals that no filtering argument exists.

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 ('Get') and a precise resource ('maker and taker commission rates') scoped to 'all markets on BitPin'. This is clearly separable from data-oriented siblings like bitpin_get_markets and bitpin_get_tickers without opening any schema.

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 the use case (looking up fee rates) and notes the authentication precondition, but never says when to reach for this versus neighboring market-data tools, nor does it name any alternative. An agent must infer the selection criteria.

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