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

Annotations only say non-read-only, non-idempotent, non-destructive; the description adds the real behavioral contract: batch of up to 50 items, upsert-by-id semantics (no id = insert, id = partial update, id + desativar = soft delete keeping history), all-or-nothing transactionality, duplicate rejection with the existing id, and the target system (upCampo). This is exactly the beyond-annotations disclosure the dimension asks for.

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 purpose and the cardinality rule, then batch semantics, then the write/confirm instruction; every paragraph carries distinct operational information. It is on the long side for a single tool, but there is little filler and no repetition.

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 values need not be restated, and the description still covers the one response detail that matters operationally (which item failed and why, on an all-or-nothing write). For a batch mutation with complex conditional semantics, nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds aggregate-level meaning the per-field descriptions do not carry: the list is a single transactional batch, items are dispatched all at once, and the id/desativar combination drives insert-vs-update-vs-deactivate. That interplay is documented in prose rather than only in field descriptions.

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 and resource in context: it records what is planted per talhão per safra, and ties the record to downstream artifacts (ordem de serviço, colheita, produtividade). That framing distinguishes it from cadastrar_safra, cadastrar_talhao and cadastrar_cultura without needing to name them.

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?

Explicit routing rules: one variety per talhão/safra, multiple varieties must go through the portal, and changing safra/talhão/cultura requires deactivating and re-including. It also tells the agent to confirm with the user before calling, which is an actionable usage condition rather than a generic disclaimer.

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