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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds value by naming the returned fields (categoría, descripción, link), which matters because no output schema exists, but it says nothing about result limits or pagination for a catalog listing.

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 that front-loads the action and resource, then appends the filter capability and return fields. No filler or repetition of the tool name.

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 read-only, zero-required-parameter listing tool with full schema coverage and no output schema, the description covers purpose, return fields, and filtering sufficiently. Remaining gaps (pagination, behavior on empty results) are minor for this complexity level.

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% and each parameter carries its own description, so the schema does the heavy lifting. The description only restates the categoria/buscar filters and never mentions the idioma enum, adding no syntax or format detail beyond the schema.

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?

Specific verb plus resource ('Lista los juegos disponibles en Rey Fortuno') with concrete category examples (slots, mesas, crash, deportes) and a statement of what each result contains. Nothing overlaps with the siblings prode or verificar-jugada, so the agent can route to it unambiguously.

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?

'Filtro opcional por categoría o texto' tells the agent that filters are optional and which ones exist, giving clear context for when to pass them. It stops short of explicit when-not guidance or naming alternatives, though the siblings are unrelated enough that exclusions add little.

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