CRM criar atividade

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

The description discloses a prerequisite (ELEVOR_ALLOW_WRITES=true) but does not describe side effects, return values, or error behavior. It only states that it creates an activity, leaving the user unaware of what happens after the call.

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 extremely concise, summarizing the action in a single sentence with a clear primary verb and resource. It is front-loaded and gets directly to the point, with no unnecessary words.

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?

The description lacks essential context such as the expected structure of the 'atividade' object, any return information, and the broader purpose of the activity within the CRM. It leaves the user guessing about the tool's full functionality and data requirements.

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?

The only parameter 'atividade' is an object with no schema definition. The description does not explain what fields or structure are expected, making the parameter completely vague.

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 the action 'Cria atividade' (creates activity) and the resource is the CRM. This distinguishes it from other creation tools like crm_criar_contato and crm_criar_conta, which create contacts and accounts respectively.

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 provides no guidance on when to use this tool instead of other CRM creation tools. It mentions a permission requirement but does not explain conditions for usage or comparisons with alternatives.

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