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

The readOnly annotation already covers safety, and the description adds useful scoping about how the theme is identified. However, it does not disclose what happens when no identifier is provided or when both caminho and area+tema are supplied, and it leaves list ordering/pagination behavior unstated beyond what the schema covers.

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 compact sentences, front-loaded with the action and resource, followed by the identification modes and the value proposition. There is no filler, and the bridge metaphor earns its place by clarifying when the tool is useful.

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?

The output schema and readOnly annotation reduce the burden for return values and safety. What keeps it from being complete is the unresolved all-optional schema: the description implies an identifier is needed but never states behavior for no arguments or conflicting identifiers, and it omits any pointer to buscar_duvidas as the search-oriented alternative.

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, and the description adds meaning by explaining the alternative relationship between caminho and area+tema and by tying caminho to ler_pagina's route. The limite parameter is left to the schema, which is acceptable since the schema already documents it.

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 the tool lists reader questions ('dúvidas') about a theme, with a specific verb and resource. It also grounds the theme identifier in ler_pagina's returned route, but it does not explicitly distinguish itself from the sibling buscar_duvidas.

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 clear context: use this when you have a theme from the acervo, identified by caminho or area+tema, and want the real questions readers discuss. It positions the tool as a bridge between the editorial acervo and reader questions, but it does not name exclusions or a preferred sibling alternative such as buscar_duvidas.

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