Create estimate

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

Beyond the annotations, the description discloses that the estimate is saved as a draft in Estimating status, uses unit-price billing, is dated today, and has totals computed by the app. It also clarifies that nothing is sent until send_estimate is invoked, which is important behavioral context for a create operation.

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 front-loaded with the core action and then efficiently covers status, billing, required relationships, item structure, and next-step tools. There is no wasted text, and each sentence adds useful context.

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 create tool with annotations and no output schema, the description covers most critical behavior: draft status, billing mode, date, totals computation, and no automatic sending. It could be slightly more complete by indicating what is returned after creation or how the new estimate id is used, but the overall context is strong.

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?

The description adds useful meaning for the core inputs: items are priced lines with name, type, quantity, unit, unit cost, markup, and cost code, and project_id versus customer_id is explained. However, with schema description coverage at 38%, several optional parameters such as exclusions, inclusions, expire_date, and the required title are not clarified in the description.

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 gives a specific verb and resource: creates a draft estimate on a project or for a customer, with priced line items. It clearly distinguishes this from send_estimate, add_estimate_items, and update_estimate by describing their separate roles.

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 explicitly states the project_id versus customer_id rule and names the alternative tools for sending, adding lines, and updating fields. The agent knows when to use this tool and when to use siblings instead.

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