inspect_input_mapping_context

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

No annotations exist, so the description carries the behavioral transparency burden. 'Inspect' implies read-only behavior and the return value is stated, but it does not explicitly confirm non-mutation, error behavior, or prerequisites.

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 short and front-loaded, with a clear purpose statement followed by a KB pointer and one useful example. No filler is present, though the KB link is somewhat ancillary.

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 one-parameter tool with an output schema, the description covers the primary task and parameter usage adequately. Missing usage guidance and explicit behavioral guarantees are gaps, but they are not critical for basic tool selection.

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 description coverage is 0%, but the parameter name 'imc_path_or_name' and the example '/Game/MCP_Test/Example' clarify that the tool accepts an asset path or name. Deeper semantics like name resolution rules or valid path formats are not explained.

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?

Description uses a specific verb ('Inspect') and resource ('Enhanced Input Mapping Context') and clearly states the output ('action/key mappings'). This distinguishes it from creation/setup siblings like create_input_mapping_context and add_input_mapping, though it does not name them explicitly.

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 when-to-use guidance or exclusions are provided. The example and KB link illustrate invocation but do not explain when this tool should be chosen over alternatives such as the create/add input-mapping tools.

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