Buscar versão específica das tabelas (REST)

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds valuable operational context beyond annotations: the exact GET endpoint, that a 404 means the version does not exist, that it does not modify local tables, and that the app must be running. No contradiction is present.

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 compact and front-loads the key scope distinction ('LADO SERVIDOR... NÃO atualiza...') before giving endpoint and failure semantics. Every clause carries information useful for correct invocation.

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 GET with one required parameter and full annotation coverage, the description supplies the endpoint, failure condition, runtime prerequisite, and scope exclusion. No output schema exists, so return details need not be explained further.

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 coverage is 100%, so the hash parameter is already documented. The description adds that the hash is MD5 and corresponds to the endpoint path parameter, giving useful format and location meaning beyond the schema's 'hashSolicitante' label.

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 ('busca') and resource ('registro de controle de uma versão pelo hash'), and explicitly distinguishes itself from the update tool by saying it does NOT update tables. An agent can identify it as a read-only server-side lookup rather than a synchronization or mutation operation.

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 says when not to use it ('NÃO atualiza as tabelas deste PJe-Calc — para isso use tabelas_atualizar') and names the alternative for updates. It also states the prerequisite that the app must be running, but does not compare against the closely related latest-version sibling rest_tabelas_ultima_versao.

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