cosmosdb_upsert_item

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

Discloses auth method (key_env_var) and required 'id' field. No annotations provided, so description carries full burden. Missing critical detail about how partition key is determined (only mentioned in text but not in schema) and potential error conditions.

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?

Short, well-structured description with clear front-loading and bulleted details. Could be slightly more concise but effectively communicates key points.

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 main behavior and return type, with output schema present. However, missing partition key handling explanation and error scenarios make it incomplete for a write operation with complex input.

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%, so description must compensate. Explains 'id' field requirement and key_env_var behavior, but does not elaborate on account, database, container, or the item structure beyond 'id'. Partial semantic support.

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?

Clearly states 'Insert or replace an item in a Cosmos DB container' with specific verb and resource. Explains upsert semantics and distinguishes from siblings like cosmosdb_read_item and cosmosdb_delete_item.

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?

Clearly describes the upsert behavior and when it creates vs replaces. However, lacks explicit guidance on when to choose this over alternative tools like cosmosdb_query_items or cosmosdb_read_item.

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