azure_get_critical_bugs

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

No annotations are provided, so the description must convey behavior. It indicates a state filter (não concluídos) but does not mention that this is a read-only operation, how results are ordered, or what the output format is. It does not disclose any side effects, authentication needs, or rate limits, leaving the agent with incomplete behavioral knowledge.

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, front-loaded sentence that directly states the tool's purpose without extraneous words. It is highly concise and easy to parse.

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?

The tool is simple (one optional parameter, no output schema), so a short description can suffice. It names the resource and filter, but it lacks explanation of the parameter and context relative to sibling tools. Given the low complexity, a minimal description is acceptable, but there are clear gaps in parameter documentation and usage context.

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 one parameter (maxResults) with 0% schema description coverage. The tool description does not mention maxResults at all, nor does it explain its purpose (e.g., limiting the number of results). Since the description is the only source for parameter meaning, this is a significant gap.

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 uses the specific verb 'Busca' (searches) and precisely identifies the target: critical bugs (priority 1) that are not completed. This clearly distinguishes it from sibling tools like azure_query_work_items or azure_get_work_item, which are more general. The scope is explicit.

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 usage for retrieving critical uncompleted bugs, but it does not provide explicit guidance on when to choose this tool over alternatives such as azure_query_work_items. No exclusions or alternative recommendations are given.

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