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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds the behavioral trait of pagination ('paginada'), which goes beyond the annotations, but does not elaborate on other behavioral aspects such as error handling or response format. It does not contradict the annotations.

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 a single, concise sentence with a clear hyphenated explanation of the hierarchy. There is no redundant information or filler. It effectively communicates the core functionality and context in minimal words.

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 simple listing operation, the description is complete: it states the resource (brands), the scope (from the catalog), and key behavior (paginated). No output schema is provided, but the description does not need to explain return values for a basic list operation. The hierarchy context further enriches completeness.

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 provides 100% coverage with descriptions for all three optional parameters (`tipo`, `pagina`, `porPagina`). The tool description itself adds no additional parameter-specific semantics beyond what the schema already describes, so it remains at the baseline for high coverage.

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 that the tool lists vehicle brands from the Carpedia catalog, and explicitly places it as the highest level of the brand → model → version hierarchy, making its purpose unambiguous and distinguishing it from sibling tools like `carpedia_buscar_modelos` and `carpedia_buscar_versoes`.

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 when to use this tool (when you need brands at the top of the hierarchy) by mentioning the hierarchical level, though it does not provide an explicit contrast with alternatives. The pagination mention also hints at usage for large lists, but lacks a direct 'use this instead of X' statement.

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