bx24_crm_quotes

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

With no annotations, the description carries the full behavioral disclosure burden, but it only lists operation categories like 'CRUD' and product rows. It does not mention that quotes can be deleted, that product rows may be fully overwritten, or that contact unbinding is destructive; the schema's action enum flags some actions as destructive, but the top-level description itself lacks this transparency.

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 a single dense sentence with no filler. It front-loads the resource and operation families, then adds API method names and multilingual terms, all of which are useful for an agent; every element earns its place.

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?

This is a complex 13-parameter, 16-action tool with no annotations and no output schema, yet the description only summarizes scope. It omits return-value expectations, prerequisites for actions, side-effect ordering, and how to choose among the many embedded actions, leaving substantial context for the agent to infer from the schema alone.

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?

Input schema description coverage is 100%, so the baseline is 3; every parameter already has a meaningful description. The tool description adds only high-level domain context and does not enhance parameter semantics beyond what the schema provides.

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 identifies a specific resource (Bitrix24 CRM quotes) and enumerates the operation families: CRUD, product rows, contact bindings, and user fields. It also names the corresponding API method groups, making the tool's scope unmistakable and distinct from sibling CRM tools like deals, contacts, or invoices.

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 no guidance on when to use this tool versus the many sibling CRM tools, such as bx24_crm_deals or bx24_crm_invoices. Usage context is only implied through the word 'quotes' and the listed method families; there are no exclusions or alternative tool references.

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