mapper_add_validation

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

With no annotations, the description carries the full burden, but it only says the action is a Pro feature and that it adds validation. It does not disclose whether it modifies project files, what side effects occur, or whether api_key is needed for the Pro gate.

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 with the action front-loaded and the Pro-feature caveat in a parenthetical. No words are wasted, though more behavioral detail would be welcome.

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?

The tool is low-complexity, but an agent still lacks enough context to safely invoke it: no side-effect disclosure, no relation to existing mapper tools, and no explanation of the api_key parameter. The Pro-feature note is the only contextual hint beyond the schema.

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 50%: directory is described but api_key is not, and the description adds no parameter-level meaning. 'Pro feature' only hints at api_key usage without tying it to the parameter, so the description fails to compensate for the undocumented parameter.

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 identifies a clear action ('Add validation') and a specific resource ('mapping layer'), so an agent can tell what the tool does. It does not explicitly distinguish itself from mapper_generate_transforms or mapper_create_layer, but the verb/resource pairing is sufficiently concrete.

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?

There is no guidance on when to invoke this tool versus siblings such as mapper_create_layer or mapper_generate_transforms. The single sentence gives no conditions, prerequisites, or exclusions, so the agent must infer the use case from the tool name.

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