styx_fees

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

No annotations are supplied, but the tool is a zero-argument read, so the behavioral burden is light. The description does disclose the return payload structure (three named tiers in sat/vB), yet says nothing about freshness, caching, data source, or failure behavior if Styx is unreachable.

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 core sentence is tight and front-loaded with the verb, unit, and tier names. The appended 'Tip:' is a cross-sell that does not help an agent invoke this tool, though it costs only one line.

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 annotations and no output schema, the description must carry the whole definition, and it does state the returned tiers and units. It leaves unclear what 'Styx' fee estimates mean relative to the general Bitcoin fee tooling in the sibling set, and gives no indication of freshness or fallback behavior.

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, so the schema is trivially complete and there is nothing for the description to disambiguate. Baseline 4 applies.

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 (get Bitcoin network fee estimates) with the return shape spelled out: sat/vB and three tiers low/medium/high. It does not, however, distinguish itself from the near-duplicate sibling `get_btc_fees`, so an agent cannot tell from this text which fee source to prefer.

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?

No statement of when to use this versus `get_btc_fees` or `get_stx_fees`, and no prerequisites or exclusions. The only guidance given is a promotional tip pointing at `earning_opportunities`, which is unrelated to fee estimation and does not help the agent choose between fee tools.

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