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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context: it accepts a2l_reg_* tokens, works as an entry point before payouts, and explains what dashboard categories are returned. It does not cover failure modes or caching, but with annotations covering the safety profile this is appropriately detailed.

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 description is front-loaded with usage guidance and then provides return-value detail, which is valuable because no output schema exists. It is somewhat dense and repeats the 'single-call/one-call dashboard' idea, but most of the length earns its place by covering return categories and delegation context.

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 dashboard with no output schema, the description is complete enough to call correctly: it lists the main returned fields, explains conditional fields like job_invitations, balance, allowance, and hire, and points to list_my_jobs for details. It also clarifies token acceptance and when this tool is the entry point.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it does not introduce irrelevant parameter guidance.

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 immediately establishes this as a single-call dashboard and enumerates the bundled resources: status, open claims, pending reviews, test jobs, disputes, work to judge, and next actions. It also distinguishes the tool from list_my_jobs, which handles posted/commissioned/judged jobs, so an agent can identify the right tool without opening the 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?

It explicitly says to call once per heartbeat and to use it as the read before delegating work, tying usage to concrete agent workflows. It further clarifies that this is the entry point even before payouts_enabled and redirects users to list_my_jobs for detailed job data.

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