get_game_catalog

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

The description adds valuable context beyond annotations: it explicitly states 'No authentication required' (which isn't covered by readOnlyHint alone) and clarifies the scope ('printable component types'). The annotations already declare readOnlyHint=true, so the description doesn't contradict them and provides useful behavioral information.

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 perfectly concise with two sentences: the first states the purpose and scope, the second adds critical behavioral context. Every word earns its place, and it's front-loaded with the core functionality.

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 simple read-only catalog browsing tool with one optional parameter and readOnlyHint annotation, the description is nearly complete. It covers purpose, scope, and authentication context. The only minor gap is lack of output format information (no output schema exists), but this is acceptable 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?

With 100% schema description coverage, the schema already fully documents the single optional parameter. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline of 3 for adequate coverage without extra value.

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 specific action ('Browse') and resource ('TGC printable component types'), with explicit examples of what's included ('cards, boards, boxes, etc.'). It distinguishes from siblings like get_component_details (specific details) or get_my_games (user-specific).

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?

It explicitly states when to use this tool ('No authentication required') and implies when not to use it (for user-specific data, use get_my_games or get_my_designers). It provides clear context for browsing general catalog vs. authenticated operations.

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