get_file_bundle

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

Discloses the 20000 char cap, a key behavioral constraint. Mentions dependency on get_review_targets, implying data flow. No annotations provided, so description carries the burden well. Could mention whether it modifies state, but mutation is unlikely.

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?

Two concise sentences covering purpose, examples, constraint, and usage hint. No fluff, front-loaded.

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?

Adequately describes the tool's behavior and dependencies for a 3-parameter tool with no output schema. References sibling tool. Slight gap: no mention of return value or side effects, but not critical for a grouping operation.

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. Description adds context for diff_ref ('pass from get_review_targets') but files parameter repeats schema description. Some added value but not critical.

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?

Clearly states the verb 'Group' and resource 'files into review bundles' with specific examples (test/source pairs, i18n variants) and a constraint (20000 char cap). Distinguishes from sibling get_review_targets by indicating that tool provides input.

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 instructs to pass diff_ref from get_review_targets, giving clear usage context. Does not explicitly exclude other scenarios, but the instruction is strong enough for most use cases.

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