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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds meaningful behavioral detail beyond annotations: pagination via offset/limit, JSON query filters, nested resource constraints with parent_id, and bulk execution via ids/parent_ids.

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 well-structured and mostly front-loaded, with the core usage in the first lines and a clean resource list. There is mild redundancy: resources are listed in prose and again in the 'Recursos' block, which costs a little conciseness without adding much value.

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 9 parameters, 12 resource enums, and no output schema, the description covers usage, pagination, nested resources, and bulk support well. It falls short of full completeness by not describing the return shape and by leaving the 'account' parameter unexplained.

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 has 0% description coverage, so the description carries the burden. It explains resource, id, limit, offset, query, parent_id, ids, and parent_ids usage. However, the 'account' parameter is not explained, and the structure of the 'query' JSON is only vaguely described as 'filtros em query JSON'.

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 identifies this as a read-only tool for Bsoft TMS trip data: 'Controle de Viagens no Bsoft TMS (leitura)'. It explains the resource-based access pattern and distinguishes this read tool from the write siblings by using 'leitura' and describing list/get semantics.

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 concrete usage guidance: pass resource + optional id for a single record, omit id to list, use offset/limit for pagination, query for filters, and parent_id for nested resources. It does not explicitly name the write sibling tools as alternatives, but '(leitura)' plus the sibling naming convention makes the read vs write split clear.

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