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

Annotations already establish readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real value beyond that: results are deterministic arithmetic with the method explained, the variance buffer absorbs overruns from fixed-price adjustments, and delivery hours are used for internal cost/capacity only and 'never shown to clients'.

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 long sentences, but front-loaded: the first sentence states what is produced, the second what goes in, the third the return surface. The exhaustive output list is long yet justified because no output schema exists; only mild density cost.

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 9 parameters, nested objects and no output schema, the description correctly carries the return-value burden (tier contents, break-even and target price, rounded recommended price, margin, overrun headroom, capacity check). The one missing piece is any positioning against the sibling pricing tools.

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 89%, so the schema already carries the parameter detail, including defaults and the core/common/premium tier mapping. The description only restates this at a conceptual level ('fixed costs, owner pay, staff, delivery capacity') without adding syntax, units, or edge-case meaning, so the baseline of 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?

The description gives a concrete verb and artifact: turning a service business's work into three fixed-price tiers, and it enumerates the inputs (cost base, deliverables tagged core/common/premium) that define scope. It never names or contrasts with siblings like stress_test_package or compare_models, so an agent can't tell from the text alone which of these pricing tools to reach for.

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?

Applicability is implied by the detailed input narrative (requires a cost base plus leveled deliverables), but there is no explicit when-to-use or when-not-to-use statement, no prerequisites, and no routing to the alternative pricing/analysis tools. The closing note about adjustments being treated as included is a modeling behavior, not usage guidance.

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