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

Adds behavior beyond the annotations: the payload is a full replace where omitted fields are zeroed, and ownership is validated via IdEmpresa. These are exactly the traits an agent needs since destructiveHint=true alone does not explain the zeroing risk, and the annotation set is consistent with the described overwrite semantics.

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 purpose, then the critical zeroing warning, then the recommended workflow. Every sentence earns its place, though the Id/payload/workflow instructions could be tightened slightly.

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 destructive 23-parameter overwrite with an output schema present, the description covers the essential risks (zeroing, ownership check, prior consult) without needing to explain return values. It could say more about what happens on validation/ownership failure, but it is sufficient to call 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?

With 23 parameters at 0% schema description coverage, the schema explains almost nothing, so the description must carry the burden. It clarifies the Id input and the all-fields-required nature of the payload, but note 'Id obrigatorio' conflicts slightly with the schema where Id is nullable and not in the required list; per-field meanings remain undocumented.

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 ('Atualiza uma regra de tributacao existente'), making the update semantics clear and distinguishing it implicitly from tributacao_criar. It does not explicitly name a sibling to route against, but 'existente' plus the consult-first workflow leaves little ambiguity.

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 a concrete prerequisite workflow: call tributacao_consultar first to fetch current data, then resend everything with modifications. It names the alternative sibling and the condition for using it, though it never states when NOT to use this tool (e.g., use tributacao_criar for new rules).

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