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

No annotations are provided, so the description carries the full behavioral burden. It implies mutation by saying corrections are applied to the batch and warns against inventing missing data, but it does not disclose side effects, reversibility, atomicity, permissions, or how the batch is modified.

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?

The description is two sentences, front-loads the action, and immediately follows with when-to-use and when-not-to-use guidance. There is no wasted text.

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?

The tool is a mutation operation with nested opaque inputs and no annotations, and the description leaves key invocation details unspecified. The output schema covers return values, but the description still lacks enough parameter and behavioral context for safe correct invocation.

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 description coverage is 0%, and the schema uses opaque nested objects. The description names 'relatório' and 'lote' but does not explain the expected structure of report.findings or how JSON Patch corrections are encoded, so it does not compensate for the schema gap.

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 states a specific verb and resource: applying JSON Patch corrections from a report to the batch. It is clear what the tool does, though it differentiates itself from siblings mainly through usage context rather than an explicit contrast in the purpose statement.

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 explicitly says when to use the tool, after tiss_validate or tiss_audit with correctable findings, and when not to use it, for inventing missing data. The alternatives and boundary condition are named directly.

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