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

Annotations already give readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is covered. The description adds behavioral context: it is a summary (Panorama) and does not list invoices. This aligns with the read-only annotation and adds meaningful detail about output scope without contradiction.

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?

Two concise sentences. The first states the core purpose and content, the second clarifies it is a single summary without detail lists. Front-loaded and free of redundancy, every word earns its place.

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 moderate complexity (4 params, no output schema) and strong annotations, the description is reasonably complete. It explains what the summary contains (sales, purchases, returns with quantities and values) and what it omits (invoice listing). Parameter specifics are only partially addressed, but the 'period' reference covers the date range. Overall, it provides sufficient context for a read-only overview tool.

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 0%, so the description must compensate. It mentions 'período' which implies data_inicial/data_final, and 'loja' is obvious, but it does not explain the 'account' parameter or provide explicit parameter-level guidance. It adds partial semantic context but leaves some parameters undocumented.

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 provides a summary (Panorama/Resumo) of sales, purchases, and returns with quantities and values for a given period in a store. It distinguishes from sibling tools like cigam_vendas (likely listing sales) by explicitly stating it is a single summary without listing invoices. The verb 'Panorama' and resource 'loja' are specific.

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 gives clear context: use this for a period summary in a store, not for detailed listings ('sem listar as notas'). It implies when to use it over more granular siblings, but does not explicitly name alternatives. Given the sibling names, the intent is clear enough to guide selection.

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