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

With no annotations, the description carries the full burden, and it does disclose the fee model itself: 8-25 bps scaling with price extremity plus an optional 0-100 bps additive partner fee. It does not state that this is a side-effect-free calculation, whether a user_id is required for tier-dependent rates, or whether the result depends on account tier.

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 states the action and then the pricing mechanics; nothing is wasted. It could still use a second sentence for parameter/usage detail without becoming bloated.

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?

There is no output schema, so the description should ideally indicate what the estimate returns (e.g. bps vs absolute fee for the given size/price), and it omits that. Combined with the near-total absence of parameter semantics, the definition is minimally viable for a 5-parameter pricing tool.

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?

Schema description coverage is 0% across 5 parameters, so the description must compensate and largely does not. It explains only additive_fee_bps (optional partner fee, 0-100 bps), leaving price, size, market_id and user_id without any format, unit, or semantic explanation (e.g. string decimals, quote vs base units, whether user_id changes tiered rates).

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?

Specific verb+resource: 'Estimate the taker fee for a hypothetical order' plus the named fee mechanism (PAX Adaptive Fee Curve). It is clearly distinguishable from siblings like pax.fee_ledger_read (historical fees) and pax.mm_stipend_estimate (market-maker stipends), though it never names those siblings explicitly.

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 word 'hypothetical' implies pre-trade cost simulation as opposed to reading actual charged fees, which is a useful usage signal. However, there is no explicit when-to-use/when-not guidance, no statement of prerequisites, and no routing to the related fee tools the sibling list exposes.

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