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

Annotations already establish readOnly/idempotent/non-destructive safety, but the description adds real behavioral context: ordering by relevance, automatic exclusion of canceled and expired agreements, cost-free nature, and the content-negotiation behavior of Accept: text/html. This is meaningful disclosure beyond the annotation profile, though it does not cover pagination or result-size behavior.

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?

Front-loads what the tool returns, then layers filtering, the adesao flag, and the related endpoint/header notes. It is dense but each sentence carries information; the back half reads as a slightly run-on sequence of notes rather than a tight statement.

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?

With no output schema, the description correctly enumerates the returned fields and ordering, and documents the validity/cancellation filter plus the HTML-tab alternative. It is nearly complete for an agent to call it correctly, lacking only pagination guidance (pagina) and result-count expectations.

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 schema already documents all three parameters; the description's restatement of adesao=1 adds little beyond it. The baseline of 3 is appropriate since the schema carries parameter meaning and the description does not extend it.

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 resource (valid framework agreements / ata de registro de preços on PNCP) and enumerates the returned fields (managing agency, validity, carona acceptance, link). An agent knows exactly what this retrieves and its ordering (most relevant first), and it is clearly distinguishable from the procurement-record lookup it references.

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?

Gives clear context: it is free, filtered to non-canceled agreements valid today or later, and `adesao=1` narrows to agreements accepting joining. It also routes the agent to the procurement record endpoint for the agreements a specific compra generated and notes the Accept: text/html variant. It stops just short of explicit when-not-to-use guidance against named siblings.

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