bx24_crm_addresses

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

Since no annotations are provided, the description must carry the full burden of behavioral disclosure. It only states 'CRUD' and 'delete by filter' without describing permanence of deletions, permission requirements, side effects, or consequences of bulk delete. The destructive flags in the action enum are part of the schema, not the description.

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 tight and front-loads the core purpose with a resource label followed by the operation summary. The REST version note and bilingual synonym list are small additions that aid retrieval without introducing significant bloat.

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 tool with 10 parameters, 8 actions, nested objects, and no output schema or annotations, the description is too thin. It omits operational details such as required fields for add, how byclient selects entities, and error or pagination behavior, leaving the schema to carry nearly all invocation-relevant 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 description coverage is 100%, so the baseline is 3. The description adds RU/EN synonym keywords and the REST method family, but it does not clarify parameter relationships, required-field rules for add, or how byclient parameters interact beyond what the parameter descriptions already cover.

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 the resource as Bitrix24 CRM addresses, enumerates the operation families (CRUD, by client, delete by filter), and names the underlying REST methods (crm.address.*, crm.address.byclient). This distinguishes it from sibling tools that target different CRM entities such as deals, leads, or products.

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 explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. Usage context must be inferred entirely from the tool name and the word 'addresses', with no routing to or away from siblings like bx24_crm_requisites.

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