update_extension

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds the crucial dry-run behavior ('Set dryRun=false to update'), clarifying that the tool can be used in a non-mutating validation mode. No contradiction with annotations.

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 short sentences front-load the key purpose and usage. No unnecessary words or repetition. Every sentence adds value.

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?

For a 3-parameter tool with no output schema, the description covers the key behavioral aspect (dry-run/mutation) and explains the main parameter (trusted code). It doesn't mention permissions or prerequisites, but annotations and sibling context suffice.

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% with good descriptions, but the description adds meaning to trustedCode as 'enable/disable full Node.js API access' and clarifies the dryRun parameter's role in mutation vs validation.

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 verb 'Updates' and the resource 'Cognigy.AI Extension settings' with a specific example 'trusted code flag'. It distinguishes from sibling tools like create_extension, delete_extension, upload_extension, and update_extension_package.

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 explicitly tells when to use it: 'Use this to enable/disable full Node.js API access' and how to invoke mutation: 'MUTATING: Set dryRun=false to update.' It doesn't explicitly state when not to use, but the sibling list provides no alternatives for updating extensions.

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