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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true). The description adds value by disclosing what the call returns — line items, totals, deposit and approval state — which is meaningful given there is no output schema. It stops short of describing not-found behavior or format of the response.

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 short sentences, zero filler, with the core operation and returned content front-loaded. The endpoint string is a compact, useful anchor for developers.

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 single-record read with no output schema, the description covers resource, identifier, and returned content, which is sufficient to invoke correctly. It omits only edge behavior such as invalid or missing ids, a minor gap given the tool's simplicity.

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?

Single parameter with 100% schema description coverage ('Invoiced estimate id.'), so the schema already carries the semantics. The description only restates 'by id' and adds no type, range or format detail beyond the schema's integer/exclusiveMinimum constraint. Baseline 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?

States a specific verb (get) and resource (estimate) scoped to a single record by id, then enumerates the payload it returns (line items, totals, deposit, approval state). This clearly separates it from invoiced_list_estimates and from the sibling get_* tools for other resources.

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?

Usage is only implied: fetch one estimate when you already know its id. The description never states when to prefer this over invoiced_list_estimates for discovery, nor any prerequisite beyond the id. Adequate for a trivial lookup, but no explicit routing guidance.

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