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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds some behavioral value by disclosing the dual output (payout plus margin comparison), but says nothing about assumptions, edge cases, or output structure.

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 first sentence is dense and front-loaded with all the substantive information. The trailing promotional URL, however, consumes space without helping an agent invoke the tool.

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?

For a six-parameter calculator with no output schema, the description covers the core computation and conceptually the returns (payout and margin comparison). It omits any description of the response shape, but given the tool's simplicity and the annotation coverage, it is largely sufficient.

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%, so all six parameters are documented in the schema and the baseline is 3. The description hints at the plan structure (base-plus-accelerator) that maps to the inputs but adds no syntax or range detail beyond 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?

States a specific verb ('Model') and resource ('a rep's commission payout under a base-plus-accelerator plan') plus a secondary function (check against gross margin). It's clear and specific, though it doesn't name a competing sibling to differentiate against, likely because none of the listed calculators cover commission modeling.

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 'to catch plans that outrun profitability' implies the use case (commission plan design and profitability sanity-checking), but there is no explicit when-to-use vs alternatives or exclusion guidance. Usage is implied rather than stated.

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