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

With readOnlyHint=true already covering safety, the description adds the non-obvious behavior: it downloads the WHOLE inventoryitem collection because Finale offers no server-side filter, which is expensive on big accounts and consumes one of 300 hourly collection reads. This is exactly the kind of hidden cost an agent needs before calling it.

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?

Front-loads the return shape before the cost warning, and every clause is load-bearing. The long second sentence is dense (payload size, rate limit, loop warning, endpoint) but not padded.

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?

No output schema exists, yet the description enumerates the returned totals and their per-location breakdown, plus the cost implications of the unfiltered fetch. An agent has everything needed to call it correctly and budget for its cost.

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 100% and product_id is already documented as the SKU, so the schema carries the parameter semantics. The description adds no syntax, format, or lookup guidance beyond confirming the scope is one product, matching the baseline for fully-documented schemas.

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 computed resource: per-product stock aggregated over Finale's stock entries, naming the exact metrics (quantityOnHand, quantityOnOrder, quantityReserved) plus per-location/sublocation breakdown. This is distinguishable from the sibling list_inventory_items, since it describes an aggregation rather than a raw listing.

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?

Gives real operational guidance ('avoid calling it in a loop', 'counts as one collection read of the 300 per hour'), but never states when to prefer this over finale_list_inventory_items or finale_list_stock_changes. Usage context is implied through the cost warning rather than through an explicit alternative.

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