mapping_update

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

Discloses full-replacement semantics (PUT vs patch), no annotations provided, but description effectively communicates the destructive nature and return value. Lacks detail on permissions or error conditions, but sufficient for a simple update.

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 key action and usage instruction. No redundant words.

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?

Adequately describes the process, prerequisites (fetch first), and return type. Lacks error handling details, but given simplicity and good schema coverage, it is complete enough.

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 100%, so baseline is 3. Description adds context about full replacement but does not significantly extend schema descriptions. The fields item constraints are already in 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 clearly states it replaces an existing mapping in full (PUT, not patch), distinguishes from mapping_create (which likely creates) and mapping_delete (which deletes), and mentions it returns the updated mapping.

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?

Explicitly instructs to fetch current mapping via mappings_list first and treat this as a full replacement. Provides clear usage context but does not explicitly state when not to use it.

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