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

Beyond readOnly/idempotent annotations, the description discloses a bug fix: the interface M/S is kept and translated to upstream 'Material/Servico', noting previous HTTP 500 failures. It also states 'Cache 1h.'

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 structured into endpoint, use-case, and correction notes. It is not overly verbose, though the correction note is detailed and somewhat extends the description.

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?

It provides enough context to invoke the tool: purpose, endpoint, use case, bug-fix behavior, and cache. It relies on the schema for pagination and parameter details and on the output schema for the return shape.

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 covers all parameters with descriptions, including the tipo M/S enum and codigo_item dependency on tipo. The free-text description adds no additional parameter meaning beyond what is in the schema, so it stays at baseline.

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 opens with a specific action and resource: 'Lista todos os PGCs que incluem determinado item de catálogo (CATMAT/CATSER).' It also states the endpoint and the intended question it answers, making its purpose unambiguous.

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?

It gives explicit guidance with 'Útil para responder: ...' and 'Insumo para ETP e benchmarking de quantitativos.' It does not compare itself to sibling PGC listing tools, so alternative selection is only implied.

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