Steam Weekly Brief

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

Annotations already declare readOnlyHint=true, so the tool is safe. The description adds value by specifying that it generates a Markdown document and includes multiple data sources, but does not contradict annotations.

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, front-loaded sentence that efficiently states purpose and scope. No superfluous words or filler.

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?

The description adequately covers the tool's purpose and main features given the presence of annotations and an output schema. However, it lacks parameter explanations and usage context, which slightly reduces completeness.

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 0% (no descriptions), and the description only hints at 'includeDiscovery' via 'optional new-game discovery'. The other three parameters (maxNewsApps, saveSnapshot, maxMetadataApps) are left completely unexplained, leaving the agent to guess their purpose.

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 clearly states the verb 'Create', the output format 'Markdown-ready weekly brief', and the specific content categories (wishlist releases, demos, price drops, etc.). It distinguishes itself from siblings like steam_game_brief (per-game) and steam_discover_games (discovery only) by enumerating its comprehensive scope.

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 implies usage via listing included features but does not explicitly state when to use this tool versus alternatives like steam_find_deals or steam_check_wishlist_updates. No prerequisites or exclusions are mentioned.

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