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

The description only says 'Create an estimate' and does not disclose any side effects, permissions, or data handling behavior. The annotations are minimal (readOnlyHint=false, destructiveHint=false) and do not add context. Although the entity parameter warns against sending sensitive data, that is a parameter constraint, not a tool behavioral trait. The description carries the burden and does not satisfy it.

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 description is a single sentence with no redundant phrases or extra details. It is concise and front-loaded with the core operation, making it easy for an agent to parse quickly.

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?

Given the tool's complexity (nested entity object, no output schema), the description is minimal but the schema carries substantial detail including required fields and data constraints. However, there is no guidance on expected return values or when to use this over related tools, leaving some gaps. Still, the overall definition is enough for a competent agent to invoke correctly with the schema alone.

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%: both entity and company parameters have descriptive text, with the entity description warning about government identifiers and card-processing details. The tool description adds no parameter information beyond what the schema already provides, which meets the baseline for full coverage.

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 states 'Create an estimate in QuickBooks Online', which is a clear, specific verb+resource statement. It distinguishes this from the many other create_* tools in the sibling list by naming 'estimate' as the resource. It is not a tautology and is unambiguous.

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 gives no guidance on when to use this tool versus alternatives like create_invoice, create_sales_receipt, or the related search_estimates/update_estimate. There are no prerequisites, exclusions, or conditions stated, so the agent must infer usage from the resource name alone.

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