Generate estimate number

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

Annotations already declare readOnlyHint=true, indicating no mutation. The description adds valuable context: it explains that the tool generates a sequential number and is needed as a prerequisite for estimate creation in certain accounts. This goes beyond the annotation by clarifying the purpose and typical invocation pattern, without contradicting the read-only hint.

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 two sentences, front-loading the primary action and then providing a crucial usage note. Every word contributes to clarity, with no fluff. It is efficiently structured and easy to parse.

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?

The tool is simple (single optional parameter, no output schema). The description covers the key purpose and when to call it. A minor gap is that it doesn't specify the return format (e.g., a string with the number), but given the tool's simplicity and annotations indicating read-only, this is acceptable for an agent to infer.

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%; the only parameter, locationId, is already described with defaults. The description does not add any additional semantics about the parameter, so it relies on the schema. Since coverage is complete, 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 clearly states the tool's function: generating the next available estimate number for a location. It uses a specific verb (generate) and resource (estimate number), and distinguishes it from estimate creation by noting it's a prerequisite for accounts that require an estimateNumber. This is unambiguous and differentiates it from sibling tools like ghl_create_estimate.

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 explicit usage guidance: 'Some accounts require an estimateNumber when creating an estimate — call this first.' This tells the agent when to invoke it (before creating an estimate) and under what condition (accounts that require it). It doesn't explicitly state when not to use it or alternatives, but the instruction is clear enough for correct usage.

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