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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's burden is lighter. It adds real value by naming the three values the tool computes — master royalty, producer's share, artist's net — which is the return content, and there is no output schema to carry that. It does not mention error behavior for out-of-range inputs, keeping it below a 5.

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?

Two sentences, front-loaded with the core purpose and output list, then a short scoping clause. No filler and nothing redundant with the schema.

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 usefully names the three returned figures, and the parameter defaults/ranges live in the schema. A pure arithmetic tool with full annotation coverage needs little more, though a note on input validity or rounding/currency assumptions would close the remaining gap.

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%, with each of the four parameters documented, including defaults for master_royalty_rate (18) and suggested_retail_price (9.99). The description mentions 'per-unit and total earnings,' which loosely maps to the units_sold conditional-total behavior, but adds no new syntax or meaning. Baseline 3 when the schema does the heavy lifting.

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?

Names a specific verb (calculate) and resource (producer points deal) and enumerates the three computed outputs: master royalty, producer's share, artist's net. It also distinguishes itself from the catalog-bound siblings by stating it works for any music, so an agent can separate it from get_track/search_catalog-driven flows 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?

The phrase 'producer points deal' and 'works for any music, not only the OnChain Music catalog' imply the usage context, but the description never states when to pick this over calculate_cowriter_split or calculate_songwriter_publisher_split, nor any prerequisites. Usage is inferable from the domain term rather than spelled out.

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