create_estimate

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

No annotations are provided, so the description carries full burden. It states 'Create an estimate' which implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether it's idempotent, rate limits, or what happens upon success/failure. The invoice comparison adds minimal context.

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 brief and front-loaded with the main action. However, the second sentence about lines format, while concise, could be more integrated or informative to earn a perfect score.

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?

Given no annotations, 0% schema coverage, but an output schema exists, the description is minimally adequate. It states the tool's purpose but lacks details on parameters, behavior, and usage context, leaving gaps for a mutation tool with multiple parameters.

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 0%, so the description must compensate. It only mentions 'Lines format same as invoices' for the 'lines' parameter, ignoring 'customer_id', 'currency_code', and 'notes'. This adds minimal meaning beyond the schema, failing to explain parameter purposes or constraints.

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 the action ('Create an estimate') but is vague about what an estimate entails in this context. It adds a comparison to invoices for lines format, which provides some context, but doesn't clearly distinguish from sibling tools like create_invoice or explain the resource's purpose beyond its name.

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?

No explicit guidance on when to use this tool versus alternatives like create_invoice or create_client. The mention of 'Lines format same as invoices' implies a relationship but doesn't specify when an estimate is appropriate over an invoice or other creation tools.

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