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

Annotations already declare the full safety profile (readOnly, idempotent, non-open-world, non-destructive), so the bar is lower. The description adds relevant behavioral context beyond that: the result is paginated, and it clarifies that 'tipo' preserves the original FIPE type. It does not add pagination edge cases, but this is solid supplemental context.

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 tight sentences with the core purpose front-loaded and no filler. The hierarchy clause adds orientation value, though it is slightly beyond bare necessity.

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 read-only paginated list tool with annotations covering safety and 100% schema coverage, the description covers purpose, pagination, hierarchy level, and filter semantics. Nothing critical is missing, though the shape of the returned brand list is left implicit (no output schema).

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 coverage is 100%, so the baseline is 3, but the description adds meaning by enumerating the categoria domain and explaining the distinction between categoria and tipo ('tipo mantém o tipo original FIPE'). This helps the agent understand why both filters exist rather than just repeating 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 verb and resource ('Lista as marcas de veículos do catálogo Carpedia') and pins its position in the hierarchy 'marca → modelo → versão', which implicitly separates it from siblings like carpedia_buscar_modelos and carpedia_buscar_versoes. An agent can identify what it returns without opening the schema.

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 hierarchy note implies this is the entry point ('o nível mais alto'), and it clarifies how to use categoria and tipo, so usage is inferable. However, it never explicitly says when to use this versus the sibling model/version tools or states prerequisites, leaving the routing to inference.

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