bulk_update_game_passes

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

With no annotations, the description covers key behaviors: sequential updates with automatic rate limiting (5 writes/second), per-item results, and non-failing items. It does not disclose authentication requirements or potential side effects, but the provided detail is commendable for a mutation tool.

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?

Three sentences, no wasted words. Front-loaded with purpose, then usage guidance, then behavioral details. Highly efficient.

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 bulk update behavior, rate limiting, error handling, and return structure. Does not mention prerequisites like permissions or universe ownership, but for a clearly described bulk update tool, this is adequate. No output schema exists, so the mention of summary and per-item results is helpful.

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%, so baseline is 3. The description adds that each entry targets one by ID and only changes provided fields, reinforcing partial update semantics. This adds modest value beyond the schema which already describes each field.

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 it updates many game passes in one call, distinguishing it from the sibling 'update_game_pass' which handles single updates. The verb 'Update' and resource 'game passes' are explicit.

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 using this instead of repeatedly calling 'update_game_pass', providing clear when-to-use guidance. Does not mention cases where it should not be used, but the context is sufficient.

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