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

Adds useful behavioral context beyond the readOnlyHint/idempotentHint annotations: 'pague por consulta' (cost per call), 'sem credenciais da plataforma' (auth model), 'não é dado sigiloso' (data sensitivity), and LGPD controller responsibility. These traits are not present in annotations and help set correct agent expectations.

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?

Four concise sentences front-load the purpose, then cover hosting/cost, data classification, and legal responsibility. The LGPD sentence is slightly regulatory but still relevant for a data-consuming tool. Efficient use of space with no redundancy.

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 read-only query tool with 5 params and no output schema, the description covers the essential aspects: purpose, official source, cost model, auth requirements, data sensitivity, and legal framing. Lacks explicit guidance on parameter combinations and expected return shape, but these are not critical for basic 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% — none of the 5 parameters (nfce, login_cpf, login_senha, pkcs12_cert, pkcs12_pass) are explained. Param names are relatively self-explanatory, but the description misses the opportunity to clarify semantics like which auth method to prefer or the format of nfce.

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 clearly states a query operation on official SEFAZ RS NFC-e (SVRS) data with 'consulta em fonte oficial'. It differentiates itself from generic platform siblings (authenticate, marketplace) but does not specify exactly what data is returned or the query scope beyond the resource name.

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?

Provides operational context: 'Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta' indicates when to use (paid hosted query, no platform auth needed), implying the authenticate sibling may not be required. However, it does not explicitly contrast with alternatives or state when NOT to use it.

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