dealdesk.list_quote_presets

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

With no annotations, the description carries the full burden, but 'List' reasonably conveys a read-only, non-destructive operation and the definition of a preset clarifies what is returned. It says nothing about scope (all presets in the project?), ordering, or whether archived presets are included — gaps that matter for a listing tool with no safety annotations.

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?

One sentence, front-loaded with the verb and resource, with the explanatory clause appended rather than preceding. 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?

An output schema exists so return values need no explanation, and the sole parameter is covered by the schema. The one remaining gap is that the description does not indicate whether the list is project-scoped or paginated, though the projectId parameter implies scoping.

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 single projectId parameter is already fully documented in the schema, including the omit-when-single-project rule, so the description need not repeat it. It adds no additional meaning about scoping or filtering beyond the schema, which is the baseline expectation at 100% coverage.

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?

Specific verb 'List' plus a precise resource 'quote presets', and it goes further by explaining what a preset actually contains (groups, lines, prices, discounts, configurations) and giving the German term. It does not explicitly contrast itself with the get_quote_preset sibling, but the list-vs-single distinction is inferable from the verb.

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 statement of when to use this versus get_quote_preset, apply_quote_preset, or create_quote_from_preset, nor any prerequisite or exclusion. The agent must infer that this is a discovery step from the verb alone.

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