boond_quotations_create

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'Create a new quotation' and offers no information about side effects, required permissions, idempotency, or what happens on success. This is insufficient for a mutating 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 extremely short, but this is under-specification rather than concise effectiveness. The single sentence 'Create a new quotation' adds no value beyond the tool name and does not earn its place in the definition.

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 tool with 7 parameters, 3 required, no annotations, and no output schema, this description is severely incomplete. It does not explain what a quotation is, what the required fields represent, how status relates to the workflow, or what the return value would be. An agent has almost no basis to call this tool correctly.

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%, and the description provides no parameter-level meaning whatsoever. Required fields like opportunityId, companyId, and total are completely unexplained. The description fails to compensate for the schema's lack of documentation.

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 'Create a new quotation' states a clear verb and resource, making the tool's basic purpose obvious. However, it adds no distinguishing detail against siblings like boond_quotations_update or boond_quotations_send; it merely restates what the tool name already implies.

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 on when to use this tool versus alternatives. The description does not mention contexts such as 'when a quote is ready to be drafted' or explicitly point to update/send for existing quotations. No exclusions or prerequisites are provided.

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