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

Annotations already declare the safety profile (non-read-only, non-destructive, idempotent), so the bar is lower, and the description still adds real domain semantics: an inactive quota never terminates respondents and records no fills. It doesn't discuss permissions or what happens to in-flight respondents at the moment of switching, which keeps it from a 5.

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?

Three short sentences, zero waste, front-loaded with the action and its argument mapping before the edge-case caveat. Every sentence earns its place.

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 idempotent toggle with no output schema, the description covers the essential semantics and the key edge case (auto quotas). It doesn't indicate how to confirm the resulting state, but annotations carry the safety profile and no return contract is expected.

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 all three parameters are already documented in the schema, including active's 'True = on.' mapping. The description's parenthetical restates that mapping rather than adding syntax or format detail beyond it, so baseline 3 applies.

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 (switch on/off) and resource (manual quota), and explicitly distinguishes the scope by naming the incompatible quota type (auto/targeting-derived). An agent can tell it apart from update_quota or freeze_auto_quota without opening either schema.

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?

Gives both the when and the when-not: use it for manual quotas, and for auto quotas use the freeze path instead (the sibling freeze_auto_quota). The condition selecting the alternative is stated, not implied.

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