list_deals

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'List' signals a read-only operation and the description mentions optional filtering and sorting behavior, but it does not disclose pagination defaults, return shape, or whether all deals are returned when no filters are supplied. These gaps are moderate but not critical for a simple list operation.

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?

A single, front-loaded sentence with no filler. It states the verb, resource, and key options efficiently, making the purpose immediately graspable.

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 five optional parameters fully documented in the schema, the description is largely sufficient. The main missing element is an explicit statement about the output format or default result set, but these are reasonably inferable from the list semantics and the select/pagination parameters.

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 description coverage is 100%, so every parameter is already documented structurally. The description only summarizes filter_stage_id, filter_assigned_by_id, and order without adding new semantic 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 uses a specific verb ('List') and resource ('CRM deals from Bitrix24'), and names the key dimensions of filtering and sorting. This clearly differentiates it from siblings like get_deal (single deal) and create_deal/update_deal (mutations).

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 clearly implies when to use this tool: when a list of deals is needed, as opposed to a single deal via get_deal. It does not explicitly name alternatives or exclusion conditions, but the context is clear and no misleading guidance is present.

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