Buscar próxima página de resultados

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

Goes well beyond the annotations (which only cover read-only/idempotent/destructive/openWorld) by disclosing that there is no local cache, that it paginates the LAST search stored server-side, and that a cache-sourced prior search is automatically re-sent live first. These are exactly the stateful behaviors an agent must know to avoid paginating the wrong result set.

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?

Front-loaded with the action and the usage trigger before the caching detail. The cache paragraph is slightly long but every sentence carries distinct, decision-relevant information, so waste is minimal.

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 pagination tool with no output schema, the description supplies the trigger, the session-state model, and the cache-recovery behavior. Nothing an agent needs to call it correctly is missing.

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 (pagina, salvar_html) are already fully documented in the schema. The description adds only the pagination concept, not parameter-specific syntax, so the 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 (advances/paginates) and resource (another page of an already-performed trademark search) and clearly separates itself from the search siblings, which start searches rather than continue them. An agent can distinguish it from every sibling without opening a schema.

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?

"Use after any of the search tools when the response indicates there are more pages" gives an explicit trigger condition and names the alternative tool category. The prerequisite (a prior search in this session) is stated, leaving nothing to inference.

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