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 genuinely useful behavior: a one-time free query per operator, a per-query charge via x402, and fleet-plan inclusion. However it never states that the operation is read-only/non-mutating, what happens on payment failure, or how the x402 flow behaves, so key behavioral traits remain unstated.

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 dense sentence front-loads the returned values, then the pricing caveat, then the parameter summary. Nothing is padded, though the telegraphic style makes some clauses (x402, fleet plan) hard to parse.

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?

The description partially compensates for the missing output schema by enumerating the returned tariff fields, and it covers payment behavior. But with 0% parameter coverage and no annotations, gaps remain around x_payment format and error/read-only semantics.

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% for all three parameters. The description only restates the schema's required/optional split ('Requires api_token, hold_id; optional x_payment') and adds no format, meaning, or expected value for any of them (e.g., what x_payment should contain).

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 names a specific operation (tariff query on a hold) and enumerates exactly what it returns: free time left, tier, next-hour cost, accrued, idle ratio. That is enough to tell it apart from a generic evaluate or register tool, though it never explicitly contrasts itself with siblings like demurrage_evaluate_hold.

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?

There is no statement of when to call this versus demurrage_evaluate_hold or demurrage_account. The only context offered is the pricing model (one free query per operator, then $0.005/query), which describes cost rather than usage conditions or prerequisites.

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