l2kc_get_quota

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

With no annotations, the description must carry the behavioral load; it does disclose two useful traits: mock data are test fixtures rather than live account data, and refresh invalidates the per-account quota cache before reading. It omits other relevant traits (read-only nature, auth/permission needs, failure modes when account or provider is unknown).

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?

Short and front-loaded, and the test-fixture warning is placed early where it matters. However the leaked RST double-backtick markup and the fragment opening ("Quota snapshots.") make it read as documentation spillover rather than agent-facing guidance, and the sentence order puts the no-rotation note before the parameter it refers to.

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, so return values need not be described, and the caching and mock-data caveats are covered. Still, for a 3-parameter tool in a duplicated gpu_/l2kc_ namespace, the missing provider semantics and the absent routing guidance versus l2kc_refresh_quota leave an agent guessing on a core selection decision.

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%, so the description is the only source of parameter meaning. It explains `account` (scoped read, no rotation) and `refresh` (cache eviction) but is silent on `provider` entirely, and gives no format hint for account/provider (name vs. id). Partial compensation only, with a full parameter left undocumented.

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?

"Quota snapshots" names the resource but supplies no verb and no scope statement, so an agent must infer that this reads quota for an account/provider. It also never distinguishes itself from the near-identical sibling gpu_get_quota, nor from l2kc_refresh_quota / gpu_refresh_quota even though it internally performs a refresh via a parameter.

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 automatic rotation" and "``account`` reads that account only" hint that a caller should pass an explicit account, but there is no explicit when-to-use guidance. Critically, the description never says when to set refresh=true here versus calling the dedicated l2kc_refresh_quota sibling, leaving a real selection ambiguity among listed alternatives.

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