listar_centros_custo

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

With no annotations, the description carries the behavioral burden and it does so well by disclosing a 24h cache, the quota-saving rationale, and the refresh mechanism. It doesn't mention return format or error behavior, but the operation is presented as a simple list.

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 sentences, no filler; the purpose and filters come first, followed by cache/refresh behavior. Every sentence 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?

For a low-complexity optional-parameter list tool, the definition covers the core call decisions: what is listed, available filters, and cache freshness. It omits return-shape and pagination details, but those are not necessary to invoke the 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?

The schema already documents all three parameters (100% coverage), so baseline is 3. The description maps 'texto' and 'empresa' to the filters and clarifies atualizar's purpose with the 24h cache detail, but adds little beyond the schema.

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?

States a specific action ('Lista') on a specific resource ('centros de custo do Sienge') and gives examples of what counts (obras, departamentos, administrativo). It is clearly not a generic list, though it doesn't explicitly separate itself from sibling listar_departamentos.

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 tells the agent the tool lists cost centers and explains when to pass atualizar:true to bypass the cache. It does not, however, give explicit guidance about when to prefer this over sibling listing tools 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.