Get estimate

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes the payload scope, which is useful because there is no output schema, but it says nothing about not-found handling, permissions, or whether the response is trimmed for large estimates.

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 front-loaded sentence with no filler; every noun phrase names a returned component. It is a sentence fragment lacking a verb, but the information density is high and nothing needs trimming.

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 simple two-parameter read tool, the annotations cover safety, the schema covers inputs, and the description covers the returned payload in the absence of an output schema. The only real gap is the lack of pointer to wave_list_estimates for discovering an ID.

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%: 'id' is documented as the Estimate ID and 'businessId' explicitly states it defaults to the value wave_get_context reports. The description adds no additional meaning about either parameter, 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 identifies the resource ('One estimate') and enumerates the contents included in the payload (items, taxes, discounts, deposit settings, payments, acceptance history, attachments), which implicitly conveys a single-record fetch. The word 'One' distinguishes it from wave_list_estimates, though the verb itself is never stated explicitly.

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 explicit when-to-use guidance, no mention of the natural alternative (wave_list_estimates to find an ID first), and no statement of preconditions or error behavior. Retrieval context is only weakly implied by the singular noun phrase.

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