Create Estimate

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

Annotations already indicate this is a write operation (readOnlyHint: false). The description confirms by saying 'Creates' and 'Returns the created estimate record.' It adds value by explaining the prerequisite and return behavior, which goes beyond the annotations. No contradictions.

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-loaded with the core action. Every phrase is informative: system, action, prerequisites, and return value. No wasted words.

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 14 parameters and no output schema, the description explains the return value ('Returns the created estimate record with its assigned number') and key prerequisites. It does not explain optional parameters, but the schema already covers them. Sufficient for typical use.

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 each parameter has a description. The tool description reinforces the need for exact match on customer_name and category, referencing search_customers. This adds minimal extra value beyond the schema, fitting the baseline of 3.

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 'Create a new estimate in Service Fusion.' It specifies the verb (create), resource (estimate), and system. It also mentions what the tool returns and prerequisites, distinguishing it from siblings like create_job or create_customer.

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 explicitly mentions requirements: 'Requires an exact customer name (use search_customers to find it) and a category.' This provides clear guidance on when to use the tool and points to a prerequisite tool. It does not explicitly state when not to use it versus alternatives, but context is sufficient.

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