breakdown_by_fee_category

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

No annotations are provided, so the description carries the full burden. It mentions the optional per-meter-size schedule and billing requirements (PREMIUM), but does not detail the response format, any rate limits, or authentication beyond billing. This provides basic but not comprehensive behavioral insight.

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 concise (4 sentences), front-loads the main purpose, and uses clear structure with examples and a list of allowed categories. Every sentence adds value with no redundancy.

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 output schema, the description hints at return values (fee lines and schedule) and covers billing. It explains the parameter alternatives and category options well. However, it does not specify the data structure of 'fee line', but given the sibling tools, this is acceptable.

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 coverage is 100%, so the schema already documents each parameter. The description adds value by clarifying the relationship between 'jurisdiction' and 'address' (alternatives) and by indicating that the output includes a per-meter-size schedule when available, which is not in the schema.

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's action ('Get every fee line within ONE named category for a US jurisdiction'), its resource (fee lines), and its scope (single category per call). It distinguishes from siblings like 'get_fee_breakdown' by emphasizing it extracts one component without parsing the whole breakdown.

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 includes explicit examples of when to use (e.g., 'what are Fresno's parks fees?') and contrasts with the alternative of 'parsing the whole breakdown'. However, it does not provide explicit when-not-to-use scenarios or directly compare to all 14 sibling tools.

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