Busca páginas do acervo jurídico brasileiro por assunto, em português. Devolve caminhos canônicos que servem de entrada para ler_pagina.
| Name | Required | Description | Default |
|---|---|---|---|
| limite | No | máximo de resultados (padrão 8, teto 25) | |
| consulta | Yes | pergunta ou termos em português, como 'produto com defeito troca' |
| Name | Required | Description | Default |
|---|---|---|---|
| paginas | Yes | ||
| total_indexado | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, and the description adds useful behavioral context: it searches only Portuguese content and returns canonical paths. This goes beyond the annotation by clarifying the tool's output role and language constraint.
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, front-loaded sentence that immediately states the verb, resource, and key constraints. No filler or redundant 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?
Given the presence of an output schema, annotations, and a sibling tool, the description is complete: it explains the tool's purpose, its language scope, and how its output connects to ler_pagina. No critical context is missing for a simple search tool.
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?
Both parameters are fully described in the schema (100% coverage), with clear descriptions for 'consulta' and 'limite'. The description does not add significant parameter-specific detail, so the baseline of 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?
The description uses a specific verb ('Busca') and resource ('páginas do acervo jurídico brasileiro') with a clear scope ('por assunto, em português'). It explicitly differentiates from the sibling tool by stating that it returns canonical paths to be used as input for ler_pagina.
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 provides clear context by establishing a workflow: use buscar_paginas to find pages, then use ler_pagina to read them. It does not explicitly state when not to use the tool, but the inter-tool relationship is implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a clearly distinct function: searching, reading, and reporting defects. There is no overlap in their purposes, and an agent would have no confusion about which tool to invoke for a given task.
All tool names follow a consistent verb-noun pattern in Portuguese (buscar, ler, relatar), making them predictable. The only minor inconsistency is the singular 'pagina' vs. plural 'paginas' in the objects, but this does not hinder understanding.
With only three tools, the server is tightly scoped to its purpose of searching, reading, and reporting issues in a legal collection. Each tool is essential and there is no bloat.
The server covers the core workflow of searching, reading, and reporting defects, which appears complete for its domain. The only gap is the lack of a way to browse or list pages without a specific search term, but this may be intentionally limited.
