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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: default result set is restricted to tools called this month, counts reset at the start of each calendar month (UTC), resetAt is the next reset timestamp, and capacityPct >= 100 means at/over cap. The 429 consequence is disclosed as the motivating behavior.

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-loads the default behavior in the first sentence, then handles each flag and the reset semantics compactly. The closing sentence is slightly redundant with the includeAllExposed pre-flight guidance, but it earns its place by naming the concrete failure mode (429).

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 no output schema, the description compensates by explaining the response surface it references (resetAt, capacityPct thresholds) and the reset cadence. Combined with full parameter documentation and annotation coverage, an agent has everything needed to call and interpret this tool.

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% and both booleans are documented in the schema, so the baseline is 3. The description still adds value by attaching a scenario to each flag (pre-flight before a long job; skipping unlimited tools), which clarifies intent beyond the schema's literal wording.

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 and resource with scope: 'Return per-tool monthly quota usage for the calling org/agent.' This is immediately distinguishable from adjacent quota/capacity siblings like get_ai_budget, get_capacity, and get_seat_count because it is explicitly per-tool, monthly, and caller-scoped.

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 clear when-to-use context: default for a small payload, includeAllExposed=true to pre-flight every registered tool before a long job, cappedOnly=true to skip unlimited tools. The final sentence adds a concrete trigger (surface a cap before a mid-flight 429). No alternative tool is named, so it stops just short of explicit when-not/alternatives guidance.

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