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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered; the description adds genuinely new behavior — that calls here are never counted against the monthly AI quota, and that the reset date is included. That quota-exemption detail is precisely what an agent needs to decide whether calling this is free. It does not mention caching or freshness of the reported numbers, 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?

It is a single front-loaded sentence anchored on "Your own budget and usage," with the quota-exemption caveat placed before the usage recommendation. The stacked colon-delimited list is dense but every clause maps to a distinct return field, so little is wasted; splitting into two sentences would read better.

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 zero-parameter, read-only, closed-world tool with an output schema, the description covers everything an agent needs: what it returns, that it is free against the AI quota, and when to reach for it. Return-value detail is delegated to the output schema, which is appropriate.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline applies. The description correctly adds nothing about inputs, focusing entirely on the return contract.

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 names the exact resource ("your own budget and usage") and enumerates the concrete payload: remaining org AI-token budget, MCP rate-limit consumption per window, this API key's toolset bundles, and mcp_calls with reset date. This is clearly distinguishable from siblings like get_my_permissions or get_business_overview, which cover permissions and aggregate business metrics rather than caller-scoped quota.

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?

It gives explicit proactive guidance: "ask here instead of guessing" and "useful ahead of large AI-compute or send workloads," which tells the agent to check quota before expensive operations. It stops short of naming a specific sibling alternative, but no plausible alternative exists for this data, so the gap is minor.

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