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

With no annotations, the description carries the full burden, yet it says nothing about whether invalid or out-of-scope XML raises an error, what the parser tolerates, or whether it is strictly a read operation. Only the word "Interpreta" hints at non-mutation.

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?

A single short sentence with no waste, but it is terse to the point of under-specification rather than efficient; nothing is front-loaded beyond the basic purpose.

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 output schema covers return values, so that need not be described, but given a parse tool over a complex EDI standard split across several sibling tools, the definition gives no guidance on accepted input variants, failure modes, or relationship to the check/build tools. It is not sufficient for confident 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?

There is one parameter ("xml") at 0% schema description coverage, and the description never mentions it — not its expected shape (raw XML string vs. base64 vs. file path), nor which document types are accepted. For a single undocumented param the description was the only place to compensate, and it does not.

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 ("Interpreta") and a specific resource ("solicitações e respostas de autorização SP/SADT"), and the 'parse' framing distinguishes it from siblings like tiss_autorizacao_build and tiss_autorizacao_check. It does not explicitly separate itself from tiss_parse_demonstrativo, which also parses TISS XML.

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?

No indication of when to reach for this tool versus tiss_autorizacao_check, tiss_autorizacao_build, or tiss_parse_demonstrativo, and no preconditions (e.g. whether the XML must be a raw SP/SADT guia or a full lote). Usage must be inferred entirely from the name.

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