list-deals

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

The annotation readOnlyHint=true already declares read-only. The description adds the HTTP method (GET), required OAuth scope (sales:read), and optional pipelineId filter, which go beyond annotations. It does not mention pagination or response format, but the schema covers pagination parameters.

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?

Three short sentences front-load the core action and then provide endpoint, filter, and scope. No redundant or vague wording; 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?

For a simple read-only list tool, the description is adequate but not complete: it omits the response shape and default behavior when no filter is provided. There is no output schema to compensate, and the description does not specify whether the result is a paginated array or summaries. However, the pagination parameters in the schema provide some 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?

Schema coverage is 100% and each parameter has a clear description. The tool description only repeats the pipelineId filter, adding no new semantic information. Thus baseline 3 is appropriate because the schema does the heavy lifting.

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?

States a specific verb and resource: 'List sales deals.' It also includes the HTTP endpoint and optional filter, making its function unambiguous. The tool name itself signals list vs. get, so it is clearly distinguished from get-deal.

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 offers no explicit guidance about when to use this tool over alternatives like get-deal; it only states the action and scope. The optional pipelineId filter and sales:read scope are prerequisites, but no direct comparison to sibling tools is provided. Usage is implied only by the tool name and the endpoint.

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