Report-Bug-To-Azure

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

With no annotations, the description carries the full burden, and it does disclose the key non-obvious behavior: it 'generates command to run' rather than directly submitting the bug. However, it omits other useful behavioral details such as the output format, whether the command is returned as a string or written to a file, and any dependency on Azure CLI being installed.

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 efficient sentence that front-loads the action and resource, with the output behavior appended in a parenthetical. The phrase 'with proper bug report structure' is somewhat vague filler, but the overall length and order are appropriate.

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?

For a 10-parameter tool with no annotations and no output schema, this description is too minimal. It does not explain the returned command's format, how the fields map to Azure DevOps work item fields, or how this tool should be selected over the direct sibling, leaving gaps that an agent must resolve elsewhere.

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 0% parameter descriptions, and the tool description adds no parameter-specific guidance. Ambiguous fields like priority (integer scale), severity ('3 - Medium' string format), project, and parent_user_story are left entirely to the agent's inference from their names.

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 states a specific action ('Report'), a specific resource ('a bug to Azure DevOps'), a concrete method ('using Azure CLI'), and the output form ('generates command to run'). The 'generates command to run' clause also distinguishes it from the sibling Report-Bug-To-Azure-Direct, which implies direct submission.

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 use when an Azure CLI command artifact is desired, but it never explicitly says when to choose this tool over Report-Bug-To-Azure-Direct or any other alternative. No exclusions, prerequisites, or when-not-to-use conditions are given.

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