invoices_create_new_estimate

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

The description provides zero behavioral information beyond what annotations already declare (readOnlyHint=false implies a write operation). It does not disclose side effects, required permissions, error conditions, or any execution details. With annotations providing minimal context, the description adds no value for behavioral transparency.

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 short phrase, which is concise but under-specifies the tool. It lacks any structure such as key points, required fields, or examples. This is not thoughtful conciseness but rather an absence of information, making it inadequate for a tool with 25 parameters.

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 the tool's complexity (25 parameters, 7 required, nested objects), the description is completely inadequate. It provides no context about required fields, how to structure items, or any high-level workflow. The schema has detailed descriptions, but the tool description itself fails to guide an agent on how to compose a valid request.

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 92%, meaning the input schema already documents nearly all parameters. The description offers no additional parameter meaning or examples, so it does not enhance understanding beyond the schema. Per the baseline rule for high schema coverage, a score of 3 is appropriate.

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 verb 'Create' and resource 'New Estimate', but it is extremely generic and does not distinguish this tool from siblings such as invoices_create_estimate_template or invoices_create_invoice. It adds no detail about what an estimate is or how it differs from related invoice tools, so it meets only the basic clarity threshold.

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?

There is no guidance whatsoever on when to use this tool versus alternatives like invoices_create_estimate_template or invoices_create_invoice. The description does not mention any prerequisites, context, or scenarios where this tool is the appropriate choice, leaving the agent to infer from the name alone.

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