upload_extension

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

Annotations provide mutability context, but the description adds that the operation is async and polls until complete, going beyond annotations. 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?

Three sentences, each essential: purpose, file format and async behavior, and dryRun guidance. Front-loaded and no wasted 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?

Covers key points (URL, tar.gz, async, dryRun) but lacks description of return values or polling process, which would be helpful given no output schema and async nature.

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?

Even with 100% schema coverage, the description adds value by stating the required file format (.tar.gz) and clarifying the dryRun parameter's effect, enriching parameter understanding.

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 'Uploads a new Cognigy.AI Extension from a URL,' using a specific verb and resource, distinguishing from sibling operations like update_extension or list_extensions.

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 notes the async nature and polling behavior, and explicitly warns about the mutating dryRun parameter. However, it does not explicitly contrast with alternatives like update_extension_package or indicate when not to use.

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