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

readOnlyHint=true already declares the safety profile, so the bar is lower; the description reinforces it ('Read-only history') and adds genuine context by naming the underlying endpoint and the fields each record carries. It does not discuss pagination behaviour or the 30-day window constraint (left to the schema), but it discloses enough about record nature and shape for a read tool.

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?

Three compact clauses, front-loaded with purpose, then scope, then return shape. No filler; the endpoint reference is short and useful for debugging/edge cases. Every sentence earns its place.

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, enumerating the returned fields (id, type, date, status, location, comments) is exactly the compensation needed, and all four parameters are fully documented in the schema. The only real gap is the absence of routing guidance versus sibling listing tools such as finale_list_inventory_transfers.

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%: limit, fields, updated_since and updated_until are all documented in the schema, including the 30-day range rule. The description adds nothing about parameter semantics, so the baseline 3 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 ('List') plus a precisely scoped resource: 'physical counts and adjustments already recorded in Finale', which implicitly separates it from siblings like finale_list_inventory_items and finale_list_inventory_transfers. The enumerated return fields (id, type, date, status, location, comments) further pin down what a 'stock change' is. An agent can identify this tool without opening the schema.

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?

Usage is implied rather than stated: 'already recorded' and 'Read-only history' signal this is a retrospective audit listing, not a mutation or a live-stock lookup. However, there is no explicit when-to-use / when-not-to-use guidance, and no sibling is named as the alternative (e.g. finale_get_product_stock for current on-hand levels vs this for historical variance records).

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