azure_analyze_cosmosdb_security

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

With no annotations, the description must disclose all behavioral traits. It states it checks and returns findings but omits details such as whether it is read-only, required permissions, rate limits, or error handling. The description lacks sufficient transparency for an agent to anticipate tool 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?

The description is two sentences: the first defines the tool's purpose succinctly, and the second lists key checks. It is front-loaded, efficient, and contains no extraneous text.

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 three parameters and no output schema, the description adequately states the tool's purpose and checks but lacks details on output structure, compliance mapping specifics, and behavioral aspects. Some gaps remain for a security analysis tool.

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%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions; it merely restates the checks performed, which is not parameter-specific. No additional context for parameters like subscriptionId or format is provided.

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 explicitly states it is a 'Cosmos DB security analyzer' and lists specific checks (public network access, firewall rules, encryption, etc.), clearly distinguishing it from sibling tools that analyze other Azure services.

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 implies the tool is for Cosmos DB security analysis but provides no explicit guidance on when to use it vs. sibling security analyzers for other services, nor any exclusions or prerequisites.

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