acr_update_registry

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'update' without mentioning permissions, idempotency, destructive potential, or error conditions. The description does not add behavioral context beyond 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 very short and to the point. However, it is too minimal and lacks depth. While not verbose, the brevity sacrifices useful 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?

With 3 parameters, no annotations, and an output schema, the description fails to provide sufficient context for the agent to select and invoke the tool correctly. It does not explain return values, side effects, or practical use cases.

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 should add meaning to parameters. The description merely restates parameter names with trivial descriptions (e.g., 'Resource group name') that add little beyond the schema. The boolean admin_enabled gets a slightly more descriptive note, but overall value is minimal.

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 'Update a container registry' with a specific verb and resource. It distinguishes from sibling tools like acr_create_registry and acr_delete_registry. However, it does not elaborate on what can be updated beyond admin_enabled, which is only hinted at in the parameter list.

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 versus alternatives such as acr_create_registry or acr_delete_registry. The description provides no context or exclusions.

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