Setell customer pricing baseline

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

The description reveals that data is sampled over 'SIGNED quotes only', which is a crucial behavioral trait beyond the readOnlyHint annotation. It also describes the row structure and the presence of a customer-wide row. This provides significant context about what the tool returns and its derivation.

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 concise at four sentences, front-loading the main action and then detailing the output. Every sentence adds value without redundancy. It is well-structured and easy to parse.

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 read-only tool with one parameter and no output schema, the description is complete. It explains what is returned, the data source (signed quotes), and provides practical use cases. No additional context seems necessary.

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 coverage is 100%, so the baseline is 3. The parameter `customerId` is already well-described in the schema with guidance on how to find it. The tool description adds overall context but no additional parameter-specific details beyond the schema.

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 reads the operator's learned pricing baseline for a specific customer. It specifies the output structure (rows per jobType scope plus customer-wide row) and fields (median, min, max, sampleSize, lastSignedAt). This distinguishes it from sibling tools like setell_get_customer_memory by focusing on pricing data.

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?

The description provides explicit use cases ('what did I charge Cooper last time?' / 'how many signed quotes does this customer have?'), giving clear guidance on when to use this tool. However, it does not explicitly mention when not to use it or alternative tools for other tasks, though the sibling list implies alternatives exist.

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