Biblioteca familiar unificada

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description appropriately does not repeat safety semantics. It adds useful context by naming the data sources and noting that owners are included, but it does not disclose return shape, ordering, or error behavior, so the added behavioral detail is moderate.

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 concise sentence that front-loads the core behavior, scope, and output emphasis without filler or repeated schema information. Every phrase earns its place.

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 parameterless, read-only tool this is largely complete: it specifies what is returned, which accounts are included, and that ownership is shown. It leaves minor ambiguity about the exact fields of the returned game list, but the absence of an output schema and the simple nature of the request make this acceptable.

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 has zero parameters and the input schema fully documents that fact, so there is no parameter burden for the description to carry. The description still adds value by identifying the configuration constants (MY_STEAM_ID and STEAM_FAMILY_MEMBER_IDS) that determine what data is returned.

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 ('Devuelve') and clearly defines the resource: a unified list of games drawn from MY_STEAM_ID and configured family member IDs, with ownership indicated. This effectively distinguishes it from sibling tools like get_owned_games, which focuses on a single user's library.

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 makes the intended use case clear: query the merged family library across configured Steam accounts. However, it does not explicitly state when not to use this tool or directly mention alternative siblings such as get_owned_games or compare_owned_games.

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