list_deny_assignments

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

The description only restates the tool's basic behavior and adds no context beyond the annotations, such as scope defaults, pagination behavior, or permissions needed. Since annotations already declare readOnlyHint, openWorldHint, and idempotentHint, this description provides no additional behavioral transparency.

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 short sentence with no redundant or filler content. It is concise and front-loaded, though it is minimal enough that it borders on under-specification.

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 tool with no output schema and only a limit parameter, the description leaves important context unclear, such as the scope of the deny assignments returned and how the result differs from the many nearby role-assignment tools. An agent could select the tool from its name, but would have weak expectations about its output and scope.

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 schema has only one optional 'limit' parameter with 0% description coverage, and the description does not mention it. While 'limit' is self-explanatory from its name and default value, the description adds no parameter-level meaning or usage hints.

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 the operation (list) and the resource type (Azure deny assignments), making it easy to tell this apart from the related role-assignment tools. It does not explicitly explain what deny assignments are or contrast with siblings, so it falls just short of a 5.

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 usage guidance is provided. The description does not say when to prefer this tool over list_azure_role_assignments, list_privileged_azure_role_assignments, or list_orphan_azure_role_assignments.

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