cosmosdb_query_items_to_file

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

In absence of annotations, description discloses key behaviors: file output, only item count returned, max_items cap at 1000, auth variation. Lacks detail on file overwrite behavior.

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?

Concise and well-structured: main action first, then details on output, limitations, and auth. No unnecessary sentences.

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 no annotations but output schema exists, description covers core functionality and usage scenario well. Some parameter details missing, but overall sufficient.

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%; description adds meaning for key_env_var and max_items (cap at 1000) but does not explain standard params like account, database, container, query.

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 runs a SQL query and saves results to a file, distinguishing it from sibling tools like cosmosdb_query_items by noting the file output and context window avoidance.

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 says to use when result set may be large, and explains auth method selection. Could be more explicit about when not to use, but guidance is clear.

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