List Setell quote tiers

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

Annotations already declare readOnlyHint and destructiveHint. The description adds that it is read-only and explains the meaning of baseIsCurrent false, as well as the ordering (most recent first). This adds context beyond 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?

Two sentences with zero waste. The main action is front-loaded, and additional detail is provided efficiently.

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 simple list tool with no output schema, the description covers what is returned (label, summary, line items, total, baseIsCurrent) and the ordering. No gaps.

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?

Only parameter jobId has full schema coverage. The description adds value by suggesting how to find the jobId (via setell_find_jobs or setell://jobs resource), which is not in the schema's 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?

Description clearly states the verb 'List' and the resource 'quote tiers for a job', and specifies the details like 'most recent first', 'label, summary, line items, total', and the meaning of 'baseIsCurrent'. It distinguishes from siblings such as setell_generate_quote_tiers and setell_select_quote_tier.

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?

Provides explicit guidance: 'baseIsCurrent: false means select will conflict; regenerate instead.' This tells the agent when to avoid selecting and to regenerate instead. However, it does not explicitly contrast with other listing or retrieval tools beyond the mention of conflict.

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