cadastrar_empresa

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the registration action without detailing side effects, persistence, authorization, duplicate handling, or changes to company data. For a mutation tool, this is a significant transparency gap.

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 concise sentence that is front-loaded with the verb and resource. It contains no redundant information or unnecessary details, making it easy to parse and act upon.

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's low complexity (one parameter, no output schema), the description provides sufficient context by linking registration to invoice issuance. It lacks explicit side-effect or response information, but for a simple create operation with a well-documented parameter schema, it is adequately complete.

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 schema description covers 100% of the parameter, describing 'dados' as a JSON string with company data (CNPJ, razão social, endereço, regime tributário, etc.). The tool description adds no additional parameter meaning beyond this, so the baseline score of 3 for full schema coverage is appropriate.

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 ('Cadastra' = registers), the resource ('nova empresa na Nuvem Fiscal'), and the purpose ('para emissão de notas fiscais'). This distinguishes it well from sibling tools like emitir_nfe, cancelar_nfe, and consultar_empresa by focusing on the creation/registration step.

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 implicitly provides usage context: it is the registration step needed before issuing fiscal notes. It does not explicitly mention when not to use it or name alternatives, but the purpose is clear enough for an agent to select it appropriately among the invoice-operation siblings.

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