navegador_ler

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

With no annotations the description carries the full behavioral burden, and it does disclose the key trait that the output includes numbered element handles ([1], [2]...) suitable for later interaction. It does not state that the operation is side-effect-free, whether reading is required after each action, or any limits on how much page text is returned.

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?

A single compact sentence with the resource and the returned fields front-loaded, no filler. The word 'de novo' is slightly ambiguous without a stated trigger, which is the only inefficiency.

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 zero-parameter read tool with an output schema, the definition is nearly complete: it names the target and the returned content. The one gap is the interplay with the numbered elements, i.e. that those numbers are the handles used by navegador_clicar, which would make the tool self-explanatory in context.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The sentence spends its words on output shape instead, which is reasonable for a no-arg tool.

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 ('Lê ... a página atual') plus the exact payload returned: título, texto and numbered elements ([1], [2]...). This clearly separates it from page-mutating siblings like navegador_clicar or navegador_abrir, though it never names the closest alternative, janela_ler.

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?

'Lê de novo' hints that this is a re-read of the already-open page, implying it follows a navigation or click action. However, no explicit when-to-use condition, no exclusion, and no mention of when janela_ler would be the right choice instead.

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