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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false. The description does not add behavioral context beyond the annotations. It mentions 'Requires the customers module active' which is a prerequisite, and 'Bulk support' which is a behavior, but it does not explain what happens on creation (e.g., required fields, side effects, idempotency). The description is vague about the actual behavior of the create action.

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 but includes extraneous information like listing all actions (list, get, create, update) when the tool is specifically for create. The 'Flattened action: create' is redundant and confusing. The bulk support note is useful but could be more concise. The description is not front-loaded with the most important information (that it creates a customer).

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?

Given the tool has 10 parameters, no output schema, and no parameter descriptions, the description is severely incomplete. It does not explain what data is needed to create a customer, what the response looks like, or any constraints. The mention of module requirement and bulk support are helpful but insufficient for an agent to correctly invoke this tool.

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 0%, so the description must compensate. The description does not explain any of the 10 parameters. It mentions 'data' as a string but does not specify its structure or required fields for creation. The 'ids' parameter is mentioned for bulk support, but not explained. The description adds minimal value beyond the schema, which is empty of descriptions.

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 states the tool is for 'Clientes' (customers) in the Kommo recurring sales/RFM module and mentions the action 'create' in the flattened action. However, it does not clearly state that this tool creates a customer; it lists multiple actions (list, get, create, update) and then says 'Flattened action: create', which is confusing. It distinguishes from siblings by the resource name (customers) but not clearly by the action.

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 mentions that the customers module must be active in the account, which is a prerequisite. It also mentions bulk support for batched execution. However, it does not provide guidance on when to use this tool versus alternatives like kommo_customers_get or kommo_customers_update, nor does it explain the context for creating a customer.

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