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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered. The description adds useful behavioral context by disclosing that results are canonical paths feeding ler_pagina, but says nothing about result ordering, corpus breadth, or why the call is non-idempotent despite being read-only.

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, zero redundancy, with the purpose front-loaded and the hand-off to ler_pagina placed second. Every clause carries information.

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?

With an output schema present and 100% parameter coverage, the description need not explain return values, yet it still names the canonical-path output and the next tool. The only meaningful gap for an agent is disambiguation from the many sibling search tools.

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 description coverage is 100%, so both parameters (consulta, limite) are already documented in the schema, including the default of 8 and the possibility of covering the whole corpus. The description only reinforces that the query is in Portuguese and subject-based; baseline 3 applies.

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 ('Busca páginas do acervo jurídico brasileiro') plus the scope ('por assunto, em português'), and points at the downstream consumer ler_pagina. It does not differentiate itself from the many sibling search tools (buscar_semantico, buscar_hibrido, search, pesquisar_fontes), which is the main remaining ambiguity.

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?

Usage is only implied: the second sentence establishes the search-then-read workflow with ler_pagina. There is no explicit statement of when to prefer this over buscar_semantico or buscar_hibrido, nor any exclusion or prerequisite, leaving the agent to infer selection among near-identical siblings.

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