compras_contrato_empenhos

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds meaningful behavioral context beyond annotations: pagination is client-side and responses are cached for 15 minutes, which helps an agent set expectations about data freshness and pagination handling.

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 extremely concise with two short sentences, and the core purpose is front-loaded in the first sentence. The endpoint, pagination behavior, and cache duration are all useful and non-redundant with the schema.

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 simple list operation with rich annotations, a full output schema, and complete parameter documentation in the schema, the description covers the essential operational details: endpoint, resource, pagination style, and cache behavior. Nothing critical for correct invocation is missing.

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 100%, so the schema already documents all three parameters. The description adds value by noting 'Paginação client-side', which clarifies that pagina and tamanho_pagina are applied client-side rather than server-side, supplementing the schema definitions.

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 states a specific verb and resource: 'Lista empenhos do contrato', and includes the endpoint path '/api/contrato/{id}/empenhos' to remove ambiguity. This clearly distinguishes it from sibling contract-related tools that deal with faturas, garantias, cronograma, or publicações.

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?

The description clearly indicates this tool is for listing contract empenhos, with the contract ID as the key input and client-side pagination behavior. It does not explicitly compare against alternatives or state exclusions, but the resource-specific endpoint and context signal make the intended use evident.

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