bx24_crm_currency

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It only says 'CRUD, base currency, localizations' and lists REST method groups, but does not disclose consequences of destructive operations, permission requirements, side effects of setting the base currency, or typical response behavior. The confirm parameter and destructive hints live only in the schema, not in the tool 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 compact, front-loaded with the resource and capability set, and avoids excessive detail. The RU/EN translation line adds mild redundancy but does not seriously bloat the text. It earns high marks for being brief and scannable.

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 9 parameters, no output schema, no annotations, and multiple operation families, the description is too sparse to be fully actionable. It does not explain how actions relate to each other, what the base currency/localization operations return, or how pagination and confirm work. The schema covers parameter semantics, but the higher-level workflow context is missing.

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 input schema already documents all parameters, including a detailed action enum. The description adds no param-level meaning beyond naming the method groups, which is acceptable given the schema's completeness. A baseline of 3 is appropriate.

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 names the resource (Bitrix24 CRM currencies) and the main capabilities: CRUD, base currency, and localizations. It also references the corresponding REST method groups, which distinguishes it from sibling tools focused on other CRM entities. However, it doesn't provide a crisp single-verb statement of what the tool does or how these operations behave.

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 implies the tool is for currency management but gives no explicit guidance about when to use it versus other tools, nor when to choose specific actions like get versus list or localizations versus base currency. It lacks any context about prerequisites or scenarios where an alternative approach would be preferable.

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