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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, and the description adds pagination, nested-resource requirements, and bulk execution behavior. It does not mention special output types for resources like conhecimentos/obterDacte or contratosFrete/pdf, but this is a minor gap given the annotation coverage.

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 front-loaded and uses clear paragraphs, but the full resource list duplicates the input schema's enum verbatim, adding length without new information. Trimming to a reference to the schema enum would make it tighter.

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 broad read-only resource tool with no output schema, it explains the generic access pattern, pagination, filters, nested resources, and bulk support. Gaps include the `account` parameter and the non-JSON/PDF nature of some sub-resources, but core usage is sufficiently specified.

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 description coverage, the description compensates by explaining `resource`, `id` vs list mode, `limit`/`offset` pagination, `query` filters, `parent_id`/`parent_ids`, and bulk `ids`. It omits the `account` parameter, leaving one of nine parameters unexplained.

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?

Description opens with 'Transporte no Bsoft TMS (leitura)', clearly stating the domain and read-only nature. It enumerates concrete resource categories (CT-e, MDF-e, veículos, agências, etc.) and the full resource list, distinguishing it from sibling bsoft_transporte_write_* tools.

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 provides explicit invocation patterns: pass `resource` with optional `id`, omit `id` to list, use offset/limit pagination, query JSON filters, and `parent_id` for nested resources. It does not explicitly name write alternatives, but 'leitura' and the sibling naming make the read/write boundary clear.

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