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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds valuable non-obvious behavior: credit numbers are live from Flow's /v1/credits, the refresh date is not exposed by the API and is shown as an estimate note, and the response includes both a human-readable summary and structured accounts/totals. This is meaningful context beyond the annotations.

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?

Three sentences, each carrying distinct information: what the tool returns, when to use it, and the response shape plus data caveat. The phrasing is slightly redundant ('account-pool control panel' and 'operator's dashboard'), but overall it is efficient and front-loaded with the most important content.

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 dashboard tool with no output schema, the description covers the key operational knowledge: output includes summary, accounts, and totals; credit data is live; the refresh date limitation is disclosed. It doesn't enumerate every field inside the accounts array, but the description conveys enough for an agent to invoke it correctly and set expectations.

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 input schema has zero parameters, which is the baseline-4 case. The description reinforces that this is a one-call, no-argument aggregate view ('one call', 'account-pool control panel'), so there is no parameter ambiguity to resolve.

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 uses a specific verb-like role ('control panel') and clearly states the resource and scope: every farm account's real credit balance, subscription tier, project count, health status, plus totals. It also gives example questions the tool answers ('how many accounts, how many credits on each and in total, what projects'), which makes it easy to distinguish from siblings like check_credits or flow_status.

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 description explicitly tells the agent when to use this tool: when the user wants the operator's dashboard view or aggregate account/project/credit questions. It doesn't explicitly contrast with sibling tools like check_credits, flow_health, or flow_status, but it provides enough context to infer the dashboard is the intended high-level overview, not a specific health or credit lookup.

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