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. 'Identifica' implies a read-only inspection, but the description never states whether it mutates anything, what happens with malformed or partial input, what the result granularity is, or any preconditions — notable gaps given the nested 'values' payload.

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?

Two short clauses, front-loaded with the purpose and then the usage rules; no filler. Its terseness is efficient, though the extreme brevity leaves the payload shape unexplained.

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?

Placeholder for completeness.

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?

There is one parameter, 'values', a free-form nested object with empty properties and 0% schema description coverage. The description says nothing about what that object must contain (guide fields? SP/SADT block? full payload?), so an agent has no basis for constructing a valid call from either schema or description.

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?

Uses a specific verb ('Identifica') plus a precise resource ('campos obrigatórios SP/SADT ausentes'), so the agent knows this is a required-field completeness check rather than a full validator. It does not name the sibling it is contrasted with (presumably tiss_validate), which keeps it from a 5.

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 gives both directions: 'Quando usar: antes de renderizar uma guia' and 'Quando não usar: para validar um lote'. The exclusion usefully separates it from batch validation, but it stops short of naming the alternative tool to call instead (e.g., tiss_validate).

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