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

Goes well beyond the annotations: all-or-nothing atomicity with the offending item reported, duplicate-name rejection returning the existing id, the rule that an OS-used subtype cannot be renamed, the AVISO when the first subtype restricts an activity type's list, and the destination store (upCampo). The soft-delete semantics ('sai das listas, o histórico fica') align with destructiveHint=false rather than contradicting it.

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?

Long but dense and front-loaded, leading with the domain concept before the operational rules and the confirm-before-calling instruction. Each paragraph carries a distinct rule, though the prose is heavier than strictly necessary for a two-parameter tool.

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?

With an output schema present, 100% schema description coverage, and full annotations, the description fills the remaining gap — atomicity, duplication handling, rename restriction and write target — so 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 real meaning: the 50-item limit, the id-vs-no-id contract for update/insert/deactivate, and the all-or-nothing consequence on the itens array. It does not clarify tipos_atividade being the COMPLETE list beyond what the schema already says.

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 (cadastrar_subtipo) and spends its opening defining the domain object (subdivision of activity type shown on the OS), including how it behaves when linked. An agent can distinguish this from cadastrar_tipo_atividade without reading either 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?

Explicitly explains the three modes — no id inserts, id updates only given fields, id + desativar deactivates — and instructs batching all user-dictated items into one call, plus a confirmation workflow. It does not name an alternative sibling for the insert case, so it stops short of full when/when-not routing.

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