totvs_tickets_filtros

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

Annotations already declare readOnlyHint=true, idempotentHint=true, etc. The description adds that it returns items with tags and clarifies parameter behavior, but does not reveal additional behavioral traits beyond what annotations convey.

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 compact—four bullet points—with the main purpose front-loaded. Every sentence adds value, and there is no extraneous or redundant content.

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 has four parameters, no output schema, and annotations providing safety hints, the description sufficiently covers what the tool does and its return type (items with tags). It could mention pagination details more explicitly, but it's largely complete.

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?

With 0% schema coverage, the description fully explains all parameters: tipo as 'product/module/routine', filtro as search text (empty = defaults), and pagination via page/page_size. This adds substantial meaning 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?

The description clearly states the tool provides 'Opcoes do catalogo para os filtros de totvs_tickets_listar', specifying the verb (options) and resource (catalog for filters). It also explains that it returns items with tags, distinguishing it from sibling tools like totvs_ticket_detalhe or totvs_contato.

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 implies usage in conjunction with totvs_tickets_listar for filtering, but does not explicitly state when to use or avoid this tool versus alternatives. No when-not or alternative tool guidance is provided.

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