get_game_data_item

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

Discloses that tool first fetches full collection then filters by id, a key behavioral trait. Lists possible collections. No annotations provided, so description carries full burden.

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 purpose, then implementation detail, efficiency tip, and reference list. Each sentence adds value, no redundancy.

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?

Covers purpose, behavior, usage guidance, and collection enumeration. Output schema exists, so return values are handled. No missing crucial info given complexity.

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?

Description lists valid collection values, adding meaning to the empty schema. However, item_id format not specified. With 0% schema coverage, description partially compensates but not fully.

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 'Return a single item from a static game data collection' with specific verb and resource. Distinguishes from sibling get_game_data_items by mentioning plural vs single.

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?

Explicitly advises to prefer get_game_data_items for multiple items, providing clear context for when not to use this tool. Implicitly suggests use for single item lookup.

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