cosmosdb_list_accounts

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

The description explains the subscription resolution process (environment variable then active login) and the error case when neither is available. Since no annotations are provided, this behavioral detail is valuable. It does not mention permissions or side effects, but for a read-only list operation, the description is adequate.

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?

The description consists of two concise sentences with no extraneous information. Each sentence serves a purpose: stating the function and explaining the subscription resolution. It is front-loaded and efficient.

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 the tool's simplicity (zero required parameters, output schema present), the description covers key behavioral aspects (subscription resolution, error handling). It does not describe the output format, but the output schema handles that. Overall, it provides sufficient context for correct invocation.

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?

The input schema has no parameters, so schema coverage is trivially 100%. The description adds value by explaining the implicit parameter (subscription) resolution, which goes beyond the empty schema. Thus, it provides useful context beyond structured data.

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 'List all Azure Cosmos DB accounts in the current subscription', specifying the verb (list), resource (accounts), and scope (current subscription). It distinguishes from sibling tools that operate on items, containers, or databases.

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 implicitly indicates this tool is for listing accounts, and sibling tools cover different operations (e.g., query items, delete items). It lacks explicit when-not or alternative guidance, but the context is clear enough.

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