check_azure_cli

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

No annotations are provided, so the description must fully convey behavioral traits. It states the tool 'checks' installation and authentication, implying a read-only operation with boolean or status response. However, it does not disclose what happens on failure (e.g., error vs false return) or whether the tool might have side effects like prompting login. The description is adequate but lacks specific return information.

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 a single, concise sentence that directly states the tool's purpose. It is front-loaded with the key action and resource, and contains no unnecessary words or information.

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 has zero parameters, no output schema, and a single sibling with no functional overlap, the description is mostly complete for its simplicity. It would benefit from mentioning the return type or value, but for a basic check tool, the current description is sufficient for an AI agent to understand the tool's role.

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?

There are no parameters, so the baseline is 4. The description does not need to add parameter information. The schema already covers all parameters (none), so no additional explanation is needed.

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 the tool checks two specific conditions: whether Azure CLI is installed and the user is authenticated. It uses a specific verb ('checks') and resource ('Azure CLI'), and distinguishes itself from the sibling tool 'get_pr_comments' which has a completely different purpose.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, or scenarios where this should be used before other CLI-related operations. The sibling tool is unrelated, so no differentiation is needed, but usage context is missing.

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