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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses the return shape (breakdown plus pricing rule) and, importantly, clarifies that the $500 Practice X-ray is a separate one-time diagnostic rather than part of the monthly figure, which prevents a costly misreading.

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?

A single dense sentence that front-loads the core purpose and appends the X-ray caveat, with no filler. It is slightly crowded, packing the main quote and the optional add-on into one sentence, but nothing is wasted.

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 two-parameter, read-only calculator with an output schema, the description covers what the agent needs: inputs, the returned breakdown and rule, and the separate X-ray cost. Return values need not be spelled out further because an output schema exists, so only the absent usage routing keeps this from being fully complete.

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 0%, so the description carries the burden, and it does map the two inputs to their business meaning ('a practice's number of locations and monthly paying patients'). However, it adds little beyond what the self-explanatory parameter names already convey and says nothing about the 1-100 / 1-250000 bounds, so it only partially compensates.

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 names a specific verb (quote) and resource (monthly Tabflows price) and states exactly what the computation is based on: a practice's number of locations and monthly paying patients. It is clearly distinguishable in intent, though it does not explicitly contrast itself with pricing-adjacent siblings like dpc_break_even or dpc_startup_cost.

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?

There is no 'when to use this' guidance, no exclusions, and no mention of when an agent should choose this over a sibling like dpc_startup_cost or dpc_break_even. The note that prices match tabflows.com/pricing is provenance, not usage direction.

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