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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: site-limited connections return countsCover scoped to granted sites while limits stay account-level, budgetModelVersion 1/2 include scheduled and on-demand buckets while version 3 omits them, and engines.daily can be empty on a legacy period. These conditional output behaviors are exactly the kind of disclosure that helps an agent interpret results.

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?

The purpose is front-loaded in the first sentence, but everything after it is one dense, run-on second sentence packed with parenthetical asides (countsCover, checkedEveryDays, budgetModelVersion). The field explanations earn their place because there is no output schema, yet a bulleted or segmented structure would make them far easier to parse.

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 parameterless read tool with no output schema, the description carries the full burden of explaining the returned payload, and it does: allowance sections, coverage semantics, ledger versions, engine selection versus daily versus on-demand lanes, and the note that write-consuming tools are absent on read-only connections. Little an agent needs in order to interpret this tool is missing.

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 nothing for the description to disambiguate at call time. The baseline of 4 applies, and the description instead spends its words on the response payload, which is reasonable given no input parameters exist.

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?

"Every allowance on this Promvia account in one read" gives a specific resource (allowances/usage) and operation (single read). It is clear what the tool returns, but it never names or distinguishes itself from nearby siblings such as get_capabilities or get_metrics, so an agent must infer the boundary.

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 closing sentence implies the use case: these are the budgets that start_citation_run, start_deep_scan and generate_brief draw on, so checking here precedes invoking them. It also notes that read-only connections will not list those write tools. There is no explicit when-not-to-use rule or named alternative, so guidance is implied rather than stated.

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