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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds a small amount beyond that by clarifying it returns raw quota data and does not perform pricing-plan inference, but says nothing about freshness, rate limits, or units of consumption.

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?

A single front-loaded sentence naming the resource first, then the boundary conditions. No padding, though the double negative phrasing is slightly less scannable than a positive scope statement would be.

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?

An output schema exists and both required params are fully documented, so the description needn't explain return values. With rich annotations covering safety and idempotency, the definition is nearly complete; only the choice versus adjacent read tools is left to inference.

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% – agent_id and channel_id are both documented with their source tools and the channel-to-agent relationship. The description adds no additional parameter meaning, so the 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?

Specific verb+resource: reads current provider quota/consumption for a channel. The scope is clear and the negative clauses ('without sending messages or inferring pricing plan') bound what the read returns. It doesn't explicitly contrast itself with siblings like provider_status or workspace_usage, so it stops 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?

The description implies usage (check how much of the provider quota is consumed) but never states when to prefer this over provider_status, workspace_usage, or line_health_read. The only guidance is exclusionary wording about side effects, not selection criteria among alternatives.

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