Get estimate

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Retrieve' aligns with those safety guarantees. The description adds only the two lookup modes and does not describe error handling or return behavior, so it provides modest extra transparency beyond annotations.

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 wasted words. The verb and resource are front-loaded, and the example is integrated naturally.

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-resource getter with no output schema, the description covers the core selection logic. The only notable gap is that it does not explicitly state that at least one of estimate_id or estimate_number is required, nor describe the return payload.

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%, so the baseline is 3. The description adds the alternative relationship between estimate_id and estimate_number and includes a concrete example format ('2025-0001'), which helps agents understand how to supply an identifier even though the schema shows no required fields.

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 a specific verb ('Retrieve') and resource ('estimate') and specifies two lookup paths: Moneybird id or the printed estimate number. This makes it clearly distinguishable from list_estimates and other single-resource getters.

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?

It gives clear context for when to use the tool: you have a known estimate id or the estimate number printed on the document. It does not explicitly name alternatives or exclusion conditions, so agents must infer when not to use it.

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