create_quote

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

The description is too brief and does not disclose behavioral traits beyond the action 'create'. Since no annotations are provided, the description carries the full burden. It does not mention permissions, side effects (e.g., whether a quote is sent immediately), or any constraints.

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 sentence, which is concise but lacks structure. It is not front-loaded with additional context. For a tool with 9 parameters, a slightly more structured description could be beneficial, though it is not overly verbose.

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 complexity (9 parameters, no output schema, no annotations), the description is incomplete. It does not explain return values, required prerequisites (e.g., client existence), or any post-creation steps. The schema covers parameters but not the overall context.

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 input schema has 100% coverage with descriptions for all 9 parameters. The description adds no extra meaning beyond 'create a new quote', so it relies on the schema. Baseline 3 is appropriate since schema does the work.

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 quote/estimate', which is a specific verb and resource. It distinguishes from sibling tools like 'convert_quote_to_invoice' or 'approve_quote', which have different actions. However, it could be more precise about what 'quote/estimate' means in context.

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 guidance is provided on when to use this tool versus alternatives. For instance, if the agent needs to create an invoice instead of a quote, the description does not differentiate. There are no explicit when-to-use or when-not-to-use instructions.

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