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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the two-mode framing and hints the tool is a 'lite' version pointing to a fuller one, but says nothing about return shape or limits beyond what annotations and the output schema provide.

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 tight sentences that front-load the core capability, with no redundant filler. The trailing promotional URL to an external full version is the only element that does not directly serve tool selection, keeping it just short of a 5.

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 pure calculator with 100% schema coverage, an output schema, and full annotations, the description supplies enough framing to invoke it correctly. It could do more to differentiate from quota-adjacent siblings, but nothing essential is missing.

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 the baseline is 3. The description conceptually maps inputs to the two methods (target/attainment for top-down, closeability for bottom-up) but adds no syntax or format detail beyond the already-documented 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 (set quotas) and resource (sales quotas) and explains the two calculation methods (top-down vs bottom-up), which helps an agent understand the output. However, it does not distinguish this from adjacent siblings like sales_rep_ramp_calculator or sdr_capacity_and_inbound_quota_planner, so it falls short of a 5.

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 implies usage by describing the two comparison modes, but gives no explicit when-to-use, when-not-to-use, or guidance about alternatives. Usage is inferred rather than stated.

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