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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: private vendor check lists and record changes are populated only for email-session requests and are empty for posting agents. It does not mention auth failure modes or size/pagination characteristics, but the access-condition disclosure is real added value.

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?

Front-loaded correctly with the action, but the payload is one sprawling run-on enumeration of a dozen item types, which is hard to scan and makes it easy to miss the actionable 'decide_by' note buried mid-list. Information-dense yet structurally unstructured.

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?

With no output schema, the description carries the full burden of describing returns — and it does so item by item, including nested fields (submission_id, checks_passed, checks_total, verdict, decision.decide_by). Combined with the email-session caveat, an agent has enough to call it and interpret the response.

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?

Single optional parameter with 100% schema description coverage; the schema already explains that agent_key is optional when the connection carries the key. The description adds no further syntax or precedence guidance, so the baseline of 3 applies.

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?

Opens with a specific verb+resource ('Read the authenticated poster's dashboard') and then enumerates the resource bundles returned (bounties, final_checks, saved jobs/verdicts, balance, settings, feeds, redeliveries, opened_pots). This clearly separates it from narrow siblings like balance_get or requester_settings_set, though it never states that contrast explicitly.

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?

Usage is implied by the aggregation scope, and one routing hint is given ('decide with bounty_pot_review; past decide_by operations reviews it'). There is no explicit statement of when to call this versus the many single-purpose sibling readers, or any prerequisite beyond the agent_key note.

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