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

Annotations only declare the safety profile (not read-only, not idempotent, non-destructive). The description adds hard behavioral facts the annotations cannot: all-or-nothing atomicity with no partial writes, the response identifying which item failed and why, duplicate-name rejection including the existing id, deactivation preserving history, and an explicit instruction to confirm with the user 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?

Front-loaded with the resource definition, then batching rules, then mode semantics, then the atomicity warning, ending with the write/confirm directive. Four short paragraphs, each earning its place. Slightly dense but no filler.

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?

An output schema exists, so return-value detail is unnecessary, and the description still covers the failure-reporting shape. For a 2-parameter batch-write tool with rich annotations and a nested-item schema, an agent has everything needed: modes, limits, atomicity, duplicate handling, and confirmation policy.

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?

With 100% schema coverage, the baseline is 3, but the description adds real semantics: the id/no-id/desativar tri-state is spelled out narratively, and it clarifies the 50-item cap and list-batching intent. It reinforces rather than merely repeats the schema, though it does not add new meaning for codigo, ciclo_dias, or tecnologia.

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 names a specific resource (variedades/cultivares) and the operation (registration into upCampo), with the constraint that each belongs to an already-registered cultura. It is clearly distinguishable from cadastrar_cultura and cadastrar_produto via the explicit 'cada uma de uma cultura já cadastrada' framing. The opening sentence reads more as a definition than a verb+action, but the intent is unmistakable.

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?

It gives concrete operating instructions: send the whole user-dictated list at once, up to 50 per call, and a clear mode table (no id = include; id = update; id + desativar = deactivate). It also tells the agent to ask the user on a duplicate-name conflict. It stops short of naming alternative tools for adjacent tasks (e.g., consultar_cadastros for listing).

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