bx24_crm_tracking

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only lists resource categories and REST versions. It does not mention mutation risks, reverseability, pagination behavior, authentication requirements, side effects, or result shapes; destructive operations are only hinted at in the input schema's action descriptions, not in the main 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 short and front-loaded with the main scope, but the RU/EN keyword list near the end adds repetitive filler rather than substantive structure. It is concise but not every token 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 multi-action tool with ten actions, nested object parameters, no output schema, and no annotations, yet the description provides only a general scope and method names. It lacks an overview of the entities' relationships, operation grouping, or any usage context that would let an agent select and invoke actions correctly.

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 schema already documents all nine parameters and the action enum. The description adds no parameter-level meaning beyond what is available in the schema, which matches the baseline of 3.

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 CRM tracking domain (traces, sources, channels) and lists the resource method groups crm.tracking.trace.*, crm.tracking.source.*, and crm.tracking.channel.*, making the tool's scope understandable. It is not a tautology and is distinguishable from the sibling tools by its tracking focus, though it lacks a single strong verb-and-resource statement.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention of what situations require this tool instead of, say, bx24_crm_deals or bx24_crm_contacts. The method list implies coverage but does not help an agent decide which operation is appropriate.

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