compras_contrato_cronograma

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

Since no annotations are provided, the description takes on full burden and effectively discloses key behaviors: client-side pagination (implied by 'paginação client-side'), potential for 200+ entries, and a 15-minute cache. This provides valuable context beyond the schema.

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 very concise at three short sentences, each providing distinct information: endpoint, pagination behavior, and caching. No extraneous or repetitive content.

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?

Given the presence of an output schema and overall tool complexity, the description sufficiently covers key operational aspects. The mention of cache duration and pagination limits offers context not present in the schema, making it reasonably complete for an agent.

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?

The schema already provides near-complete descriptions for all three parameters (pagina, id_contrato, tamanho_pagina). The description adds no additional parameter-level context beyond what the schema covers, so baseline 3 is appropriate.

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 it lists the financial schedule for a contract, identifying the resource and specific endpoint. It clearly distinguishes this tool from siblings like compras_contratos_listar by focusing on the financial timeline.

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 mentions client-side pagination and cache expiration, giving implicit usage guidance for handling large or repeated data. However, it does not explicitly state when to use this tool over alternatives or 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.