novacrm_create_client

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about what happens on duplicate names or e-mails, whether creation triggers automations/webhooks in the store, permission requirements, or what the response contains. Only the bare fact of creating a client record is conveyed.

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?

One front-loaded sentence with zero waste, but it is terse to the point that nothing beyond the core verb phrase is communicated. Efficient structure, minimal content.

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 an 8-parameter mutation tool with a nested address object, no output schema, and no annotations, the description is far too thin. It never explains accepted values for 'status' or 'clientType', the shape of 'address', or what the created client identifier looks like in the response.

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 every one of the 8 parameters already has an inline description. The single sentence adds no meaning beyond the schema, which is exactly the baseline-3 case when the schema does the heavy lifting.

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 a specific verb and resource ('Cadastra um novo cliente'), making the create-client action unambiguous. It does not distinguish itself from siblings like novacrm_create_product or novacrm_create_opportunity, relying on the tool name for that separation.

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 novacrm_import_clients (bulk creation), novacrm_update_client, or novacrm_create_opportunity for a client that is also a sales lead. The agent must infer the choice entirely from the tool name.

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