bulk_set_button_mapping

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

No annotations provided, so description compensates well. It discloses that invalid activities are skipped (with reason), a backup is created before batch, and the default is dry_run=True. These behavioral traits are crucial for the agent.

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 sentences, very concise, front-loaded with the core action, then key details. No wasted words.

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?

Given 9 parameters and batch operation, description covers filtering, safety (backup, dry run), and error handling (skip invalid). It doesn't detail the output schema, but since one exists, the agent can infer return structure. Overall complete for the 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?

Schema coverage is 0%, so description must add meaning. It explains activity_ids and name_contains as filters, button/command/entity_id as the binding, and dry_run. However, it does not describe host, params, or press (default is short_press), leaving gaps for secondary parameters.

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 tool's purpose: 'Set the same button binding across many activities at once.' It provides an example (routing VOLUME_UP) and distinguishes from sibling set_button_mapping (single activity) through the 'bulk' aspect.

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 mentions filtering options ('Filter with activity_ids and/or name_contains') and the behavior when no filter is applied ('all activities'). It also indicates dry_run default and how to apply. While it doesn't explicitly state when not to use, the sibling context (set_button_mapping for single) is implied.

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