acr_get_credentials

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

No annotations provided. Description only mentions 'get' implying read operation, but no disclosure of behavioral traits such as authentication requirements, credential format, or whether it works only with admin-enabled registries.

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?

Description is short but includes a parameter listing in docstring format which is redundant with the input schema. It is front-loaded with purpose but wastes space on parameter repetition.

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?

No explanation of return values despite having an output schema. Missing critical context such as credential type (admin user/password vs token), whether it returns JSON, and any side effects.

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 0%. Description lists parameter names ('resource_group', 'registry_name') without adding new meaning beyond what the names imply. No details on expected values, constraints, or examples.

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 'Get login credentials for a container registry' clearly defining the verb (get) and resource (login credentials for container registry). It distinguishes from sibling tools like 'acr_get_login_server' which retrieves login server URL.

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 on when to use this tool vs alternatives like acr_list_registries or acr_show_registry. No prerequisites or context provided.

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