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

Annotations already flag non-readonly, non-idempotent, destructive; the description goes well beyond by disclosing the one-call doubling cap, the mandatory repetition pattern for larger asks, the monotonic (up-only) constraint, and the manual_action_required return path with its console URL and request_text. This is unusually rich behavioral disclosure.

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?

Front-loaded with the core action and pushback/relay guidance, and nearly every sentence carries a distinct operational rule. It is dense and slightly long, but the length is justified by the multi-provider complexity rather than padding.

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 output schema exists, yet the description fully describes the two possible outcomes (submitted vs manual_action_required with its payload), the provider coverage, and the increment limits. An agent has everything needed to invoke and interpret the result.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it ties new_limit to the one-call doubling ceiling and the repeat-to-exceed pattern, and ties location/dimension to Azure-specific requirements. The per-parameter value-add is modest but genuine.

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?

States a specific verb+resource (raise a cloud-provider limit for a credential) and a second distinct mode (produce the exact manual request when no API exists). This cleanly distinguishes it from the sibling get_provider_quotas and from the more generic request_limit_increase.

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?

Explicitly says to call get_provider_quotas first and why (it names dimensions and whether the provider is automatable). It also gives a clear when-not/alternative path: for non-Azure providers the call still succeeds and returns manual_action_required, which should be relayed rather than retried.

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