Generate Setell quote tiers

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds context: it stores options as a group, does not modify the active quote, and is plan-gated. This provides useful behavioral insight beyond the 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?

The description is compact with no filler. Core purpose is front-loaded, followed by tier definitions, behavioral notes, and follow-up guidance. Every sentence adds value.

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?

Covers key aspects: tier definitions, storage, non-modification guarantee, quota, and edge case. Lacks details on output format or what 'stores as a group' entails, but overall sufficient for an agent to use 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?

The sole parameter jobId is described in detail: its current quote becomes the BETTER tier, and we provide lookup hints via setell_find_jobs or the setell://jobs resource. This adds meaning beyond the schema's basic description.

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 tool generates three quote tiers (good/better/best) around a job's current quote, with each tier defined. It distinguishes from sibling tools like setell_get_quote and setell_select_quote_tier by specifying its unique role.

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?

Explicitly states when to use (generating tier options), what it does not do (does not change active quote), and what to do next (call setell_select_quote_tier). Also mentions plan-gated usage and the 'no_quote' edge case.

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