get_input_mapping_context

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

No annotations provided. Description states it's a read operation returning mapping details. No side effects or limitations disclosed, which is acceptable for a simple read but not comprehensive.

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, front-loaded with purpose. No unnecessary words; every sentence adds information.

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?

Output schema exists, so return value documentation is covered. Missing parameter documentation is a gap, but overall sufficient for a read operation on a single-parameter tool.

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 only parameter 'asset_path' has 0% schema description coverage and the description does not explain its meaning or format. The tool name and context hint it's a file path, but the description adds no value.

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 clearly specifies verb 'Read' and resource 'key mappings from an Input Mapping Context'. It distinguishes from sibling tools like list_input_mapping_contexts (which lists contexts) and add_key_mapping (which modifies).

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 explicit when-to-use or when-not-to-use guidance. Usage context is implied (reading existing mappings) but no alternatives or prerequisites mentioned.

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