explain_mapping

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

No annotations are provided, so the description carries the full burden. It states the action but does not disclose the output format, whether the parameter is optional, or any specific behavior beyond 'explain'. For a read-only explanation tool, the risk is low, but the lack of detail about response or parameter behavior leaves gaps.

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 a single concise sentence, front-loaded with the verb 'Explain'. It avoids unnecessary words and is easy to parse.

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?

This is a simple tool with one optional parameter and no output schema. The description provides the core subject but does not describe the expected return format or any additional context about epistemic vectors or musical parameters. Since there is no output schema, the description should at least hint at the nature of the explanation, which it does not.

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 schema fully describes the single parameter 'vector' with 'Specific vector to explain (optional, explains all if not provided)', which is 100% coverage. The tool description adds no additional parameter information, so it does not augment the schema.

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 uses the specific verb 'Explain' and clearly identifies the resource: 'how epistemic vectors map to musical parameters'. This distinguishes it from sibling tools like generate_pattern or get_pattern_url, which perform generation or fetching. It is clear and specific.

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?

The description does not explicitly state when to use this tool over siblings or provide exclusions. There is no mention of alternatives or prerequisites. However, the purpose itself implies it should be used when the user seeks an explanation of the mapping concept, so usage is implied rather than explicit.

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