compras_detalhar_preco_material

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fully discloses that this tool does NOT return price, documents the exact fields in the upstream DTO, confirms the absence of price field via two verification methods, and specifies a 10-minute cache. This is exemplary transparency beyond structured data.

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 well-structured with a bold warning, clear sections for endpoint, data fields, verification, and usage guidance. It is slightly lengthy due to detailed audit documentation but every sentence adds value. The critical information is front-loaded with the 'no price' warning.

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 tool's complexity (5 parameters, 100% schema coverage, existing output schema), the description is exceptionally complete. It explains the tool's purpose, limitations, data fields, verification methodology, cache behavior, and correct alternative for price queries. No gaps remain for an agent to use this tool correctly.

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% with all parameter descriptions provided, so baseline is 3. The description adds value by explaining the scope (lists purchases for a CATMAT item), the endpoint path, and the data_fim/data_inicio default behaviors. However, it doesn't explicitly describe the pagination or codigo_item_catalogo parameters beyond the schema. The price disclosure context does not enhance parameter understanding further.

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 the tool lists individual purchases of a CATMAT item without price data. It specifies the exact DTO fields returned and differentiates from the sibling tool 'compras_pesquisar_preco_material' for price queries.

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 explicitly states when to use this tool (detailed item description, purchase object, idCompra tracking) and when not to (for unit price), directing the agent to the correct alternative 'compras_pesquisar_preco_material'. It also explains the data source limitation with audit evidence.

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