remove_mapping_trigger

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

The description does not disclose any behavioral traits beyond the action itself. It does not mention irreversibility, side effects, permissions, or return values. No annotations are provided to supplement this.

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?

The description is concise and front-loaded with the main action. Every sentence is necessary. However, it could be better structured (e.g., bullet points for args) but remains 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?

For a simple removal tool with three parameters, the description covers the basics. However, it lacks mention of return values (though an output schema exists), behavior on invalid indices, or how to obtain trigger indices. Could be more complete given no annotations.

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?

The Args block provides clear explanations for all three parameters, compensating for the 0% schema description coverage. Each parameter's purpose is concisely explained, e.g., 'Path to the IMC asset' for context_path.

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 removes a trigger from a mapping in an Input Mapping Context. The verb 'remove' and resource 'trigger' are specific, and it distinguishes from sibling tools like add_mapping_trigger or remove_mapping_modifier.

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 like remove_mapping_modifier or add_mapping_trigger. The description does not mention prerequisites, context, or conditions for appropriate usage.

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