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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: which records are importable by ID versus advisory-only, the explicit warning not to copy product data ('Não copie: cadastre com o que o cliente confirmar'), and the scale constraint on produtos. Minor gap: no mention of result limits/pagination beyond the schema's limite.

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-loads the one-sentence purpose and then uses a scannable bulleted list keyed to the enum values, so every bullet maps to a branch the agent must choose between. It is somewhat long, but the length is earned by six views that need differentiation.

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 explanation is unnecessary. The description covers all six view branches, the suggestion-vs-import distinction, and ID hand-off; combined with the rich schema descriptions (including the fazenda default), an agent has everything needed to call it correctly.

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 goes further by expanding each 'visao' enum value into an explanation of its content and downstream use, which the schema only labels. It also reinforces how the returned codes (ID_CULTURA_BASE, ID_MODELO, CODIGO) should be consumed.

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 (query the upCampo reference/help base) and then decomposes the six 'visao' values, explaining exactly what each returns (phenological stages, activity-type models with NATUREZA, product classes, products, equipment types, units). It explicitly links each result to the sibling registration tool it feeds (ID_CULTURA_BASE -> cadastrar_cultura, ID_MODELO -> cadastrar_tipo_atividade), so an agent can distinguish it from the cadastrar_* and consultar_* siblings without opening any schema.

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 per-view usage context: 'produtos' requires a search because there are 1000+, models are chosen by nature and name, and results are described as either carried into the farm (culturas, tipos_atividade) or merely suggestive (classes, produtos, tipos_equipamento, unidades). It does not explicitly say when to prefer this over lookalikes such as consultar_cadastros or buscar_ajuda, so routing to alternatives is only implied.

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