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

Annotations already cover idempotency (idempotentHint=true) and non-destructiveness (destructiveHint=false). The description adds meaningful behavioral context: that freezing prevents the quota from filling and from being rebuilt on audience changes, and that unfreezing restores normal behavior. No contradiction with annotations.

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, front-loaded sentence that places the key action and the dual-mode (freeze/unfreeze) up front. There is zero wasted text; every clause contributes to understanding the tool's behavior.

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 simple 3-parameter tool with full schema coverage and annotations covering idempotency and safety, the description is complete. It explains the tool's purpose, scope (auto quotas), and the exact effect of the boolean parameter. No output schema exists, so return values are not a gap.

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 100%, so all parameters are already documented in the schema. The description adds no extra parameter meaning beyond what the schema provides (e.g., 'disabled' already described as 'True = frozen'). The tool description simply restates the freeze/unfreeze semantic already implied by the parameter.

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 a precise verb ('Freeze') and a specific resource ('auto-generated (targeting-derived) quota'), and explains the effect (never fills, never rebuilt on audience changes) while covering the inverse via 'disabled=false unfreezes'. This clearly distinguishes it from generic quota tools like update_quota, which would handle manual quotas.

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?

The description specifies the context of use (auto-generated, targeting-derived quotas) but does not explicitly name alternatives or state when not to use it. The wording implies it is for auto quotas only, which is clear enough given the sibling set includes manual quota operations.

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