b24_crm_update

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

With no annotations, the description carries full burden. It indicates mutation but fails to disclose partial update behavior, permission requirements, side effects, or idempotency. Minimal behavioral context.

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 single sentence is concise and to the point, with no redundant information. However, it lacks any structural formatting (e.g., sections) that might aid scanning.

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 6 parameters, no output schema, and no annotations, the description is far too brief. Missing details about return values, error handling, parameter roles, and when to use webhook_url. Incomplete for effective agent use.

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 only 17% (only fields has a description). The description does not explain the remaining 5 parameters (entity, entity_type_id, params, webhook_url), nor does it add meaning beyond the schema's minimal annotation.

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 states it updates fields of an existing CRM record, distinguishing it from create, delete, get, and list siblings. However, it lacks specificity about CRM entity types (e.g., leads, deals), which are hinted by the entity parameter.

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?

No guidance on when to use this tool versus alternatives like b24_crm_create (for new records) or b24_crm_delete. Does not mention prerequisites or conditions for updating records.

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