acr_list_repositories

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

With no annotations, the description must disclose behavioral traits. It only states the basic operation (list) without mentioning read-only nature, pagination, error conditions, or any side effects. The agent has to infer safety from the action name.

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 extremely concise (3 lines) with no extraneous content. However, it borders on under-specification, sacrificing completeness for brevity. It is adequately structured but too spare.

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?

Despite having an output schema, the description fails to mention that it returns a list of repository names, nor does it cover pagination, error handling, or typical usage patterns. For a simple list tool, it is incomplete and leaves the agent guessing about common expectations.

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 description coverage is 0%, so the description must compensate. The 'Args' section provides one-line descriptions ('Resource group name', 'Name of the container registry') that add minimal value beyond the parameter names. They lack details on constraints, format, or sources for these values.

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 repositories in a container registry', specifying a concrete verb and resource. It is distinct from sibling tools like acr_list_tags or acr_list_registries, though it does not explicitly differentiate itself.

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 such as acr_list_registries or acr_list_tags. There is no mention of prerequisites, context, or conditions that would help the agent decide applicability.

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