set_input_map

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

The description uses 'replace entire', implying destructiveness, but does not discuss consequences (e.g., loss of previous mapping), required permissions, or side effects beyond the action described.

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?

Single, concise sentence that conveys the core functionality without extraneous 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?

For a simple mutation tool with one parameter, the description sufficiently explains the purpose. However, it could benefit from mentioning that the input map is completely overwritten, though this is implied by 'replace entire'.

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% for the single parameter 'actions'. The description adds no additional meaning beyond the schema's own description, so baseline score of 3 is appropriate.

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 action ('replace'), the resource ('entire input map'), and the scope ('entire'), distinguishing it from sibling tools like 'add_input_action' and 'set_input_action' which handle individual actions.

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?

No guidance on when to use this tool versus alternatives. Siblings like 'add_input_action' exist, but the description does not mention them or provide conditions for when replacement is appropriate.

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