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

Annotations only flag a non-idempotent, non-destructive write. The description adds high-value behavior beyond that: the all-or-nothing transaction ('se um item for recusado, NENHUM é gravado'), the duplicate-name rejection with the existing id, and the requirement to preview and confirm before calling.

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?

Every sentence carries a distinct instruction (source preference, batch semantics, transaction behavior, duplicate handling, confirmation step) with no filler. The opening fragment 'Culturas da empresa' is a slightly abrupt hook rather than a clean lead, and the density makes it a bit blocky.

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 a mutation tool with an output schema, the description covers the missing pieces: write semantics, transactionality, batch limits, default farm behavior, and error reporting ('a resposta diz qual item e por quê'). Nothing an agent needs to invoke it safely is absent.

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 coverage is 100%, so the baseline is 3. The description still adds meaning: it frames 'itens' as a batch with a 50-item cap and explains the id/desativar/id_cultura_base tri-mode semantics and the default-fazenda behavior in narrative form, going beyond restating the schema.

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?

States a specific verb (cadastrar/GRAVA) and resource (culturas da empresa) and points to the authoritative source (consultar_base_upcampo). It is clear what is written, though it does not explicitly distinguish itself from close siblings like cadastrar_variedade or cadastrar_safra.

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?

Gives explicit when-to-use guidance: prefer importing from the upCampo base, send the whole dictated list in one call (max 50), include vs alter vs desativar driven by the id/desativar flags, and ask the user before overwriting on a duplicate-name rejection. Alternatives and conditions are spelled out, not implied.

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