list_deals

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

No annotations provided, so description must carry full burden. Mentions read-only tier and pagination, but fails to disclose behavioral traits like access scoping, rate limits, or whether response order is guaranteed. Minimal value beyond obvious list behavior.

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, front-loaded with purpose. Could be tighter by omitting create-related information that distracts from the list operation. Efficient but not maximally concise.

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?

Given no output schema, description provides pagination and readonly hints, but lacks details on response structure, error handling, or field value limits. Adequate for a simple list tool but not fully complete.

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%, baseline 3. Description adds value by specifying default properties returned and clarifying that the 'after' parameter handles cursor pagination. Also notes default pipeline for creation, though not directly relevant to listing.

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?

Clearly states tool lists 'deal records' and differentiates from sibling tools like get_deal. However, mentions create requirements (dealname, dealstage required on create) which are irrelevant for a list operation, causing minor confusion.

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 pagination details and maps to a specific API endpoint, but lacks explicit guidance on when to use this vs. get_deal or other list tools. No when-not-to-use or exclusions stated.

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