contar_preenchimentos

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior: fixed 1-call cost, that an invalid filter is rejected before hitting the API, and that the response includes total plus projected call/quota cost. This is solid added context, though it stops short of describing the exact response shape (no output schema exists to cover it).

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?

Front-loaded with the core purpose, then cost and usage guidance. Dense with parentheticals (cota, peso da v2, páginas) but every sentence carries information; no filler.

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 9-parameter, read-only count tool with no output schema, the description covers purpose, cost model, ordering, and validation behavior. The only gap is that the exact returned fields are described only loosely, but the essentials for correct invocation are present.

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 100%, so baseline is 3. The description adds meaning beyond the schema by explaining that tamanho_pagina drives the conversation-page cost estimate and that export uses pages of 500, tying parameters to a concrete outcome.

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 verb and resource ('Conta quantos preenchimentos') plus the key scope qualifier ('sem trazê-los'), which cleanly separates it from buscar_preenchimentos and exportar_preenchimentos. An agent knows immediately this is a cheap count operation, not a fetch.

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?

Explicitly instructs 'Use SEMPRE antes de buscar ou exportar' and names the two downstream siblings it should precede. It also tells the agent it can compute the cost of either path (conversation reads vs file export), giving clear when-to-use guidance.

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