create_mapping_run

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains bypassing map-trigger but does not describe side effects, permissions, or whether the operation is long-running. Lacks detail on what happens post-creation.

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 very concise: one summary line, one usage guideline, and a cleanly formatted argument list. No unnecessary words or redundancy.

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?

Given the tool's complexity (11 params, output schema exists), the description covers the essential context. Comparison with trigger_scan is sufficient; other siblings are distinct. Could include a note about prerequisites or that it's an advanced operation, but mostly complete.

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 0% but the docstring adds semantic value for most parameters (e.g., 'JSON array of repository URL strings'). Describes format and purpose, though some parameters like credentials_profile could use more detail.

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 the tool creates a mapping run directly on the mapper, bypassing map-trigger, distinguishing it from trigger_scan mentioned explicitly. Verb 'Create' and resource 'mapping run' are specific and unambiguous.

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?

Provides explicit guidance: 'Use this instead of trigger_scan when you need full control over scope or when map-trigger is returning errors.' This tells the agent exactly when to prefer this tool over a key sibling.

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