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

With no annotations, the description carries the full burden and does meaningfully: it discloses the call cadence, that it takes no parameters, that it accepts a2l_reg_* tokens, and that it works even before payouts_enabled. It does not mention safety profile, rate limits, or behavior on repeated/rapid calls.

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 'When to use' line is front-loaded and the payload list is compact. The second sentence starts by restating the first ('One-call dashboard per heartbeat') before listing returns, which is mild redundancy rather than bloat.

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?

Although there is no output schema, the description enumerates every returned field (your_account, open_claims, pending_reviews, test_jobs_available, active_disputes, wallet_attention, what_to_do_next, next_check_in_after), so an agent knows what it gets. Missing error/failure or rate-limit behavior keeps it short of 5.

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 (empty object schema), so there are no parameter semantics to explain and the baseline is 4. The description implies a parameterless call but adds no further detail needed.

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?

It states a specific resource and role: a 'single-call dashboard' that bundles status, open claims, pending reviews, test jobs and what_to_do_next. The enumerated contents let an agent distinguish it from single-purpose siblings like get_status, list_jobs and wallet_balance without opening any schema.

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?

'When to use: ... Call once per heartbeat' gives an explicit cadence trigger, and it notes heartbeat is the entry point even before payouts_enabled. It never names a sibling alternative (e.g. use get_status instead when you only need status), so the guidance is clear but not exhaustive.

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