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

Annotations already establish this as a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so no credit is needed for safety disclosure. Beyond that, the description adds almost nothing: it does not state whether utilization is a fraction or percentage, what happens when used exceeds quota (negative remaining vs. clamping), or what the response looks like — and with no output schema, that burden falls entirely on the description.

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 with no filler or redundancy. It is tightly worded, though the brevity comes at the cost of the missing semantics noted elsewhere rather than being a model of efficient completeness.

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 trivial two-integer computation, the description is enough to understand the broad operation, and the read-only annotations cover the risk profile. However, with no output schema and no parameter descriptions, an agent cannot know the return shape (two values? one ratio?) or the units, which are genuinely needed to use the result correctly.

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 0%: both required parameters (quota, used) are bare integers with no documented units, ordering, or constraints. The description only loosely gestures at them via the words "quota" and "utilization" and never clarifies that "used" is consumed quota against a total, so it fails to compensate for the coverage gap.

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 pairs a specific verb ("Calculate") with a specific resource ("remaining agent API quota and utilization"), so the operation is unambiguous. It does not differentiate itself from the sibling privi_pro_quota_burn_rate, which also concerns quota math, so an agent must guess which one to pick for burn-over-time questions.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The description never says whether this is for point-in-time snapshots versus projections (burn rate) or what to do when the inputs are stale, leaving selection between the quota-related siblings to inference.

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