kommo_create_status

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

No annotations are provided, and the description only states it creates a stage. It does not disclose behavioral traits such as idempotency, side effects, or specific permissions required. The description adds no detail beyond what is implied by the verb 'cria'.

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 a single, efficient sentence with no redundancy. It lacks formal structure (e.g., bullet points) but is not verbose, making it easy to parse.

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?

Without annotations or an output schema, the description is insufficient. It does not explain what the tool returns, error conditions, or how it integrates with other tools. For a creation tool, key context is missing.

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 description mentions the key parameters (pipeline_id, name, optional sort/color) and their role, partially compensating for the schema's 50% description coverage. However, it does not explain the meaning of 'name' or 'pipeline_id' beyond their names, limiting added value.

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 tool creates a new stage ('etapa') within a pipeline, using a specific verb and resource. However, it does not differentiate from other creation tools like kommo_create_lead or kommo_create_contact, though the name implies status creation.

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 (e.g., why not use update_status or pipelines). The parenthetical 'desenvolver etapas' implies usage for stage development, but no exclusions or prerequisites are mentioned.

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