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

With no annotations, the description carries the full burden and does disclose a real behavioral constraint: private vendor check lists and record changes are only returned for email-session dashboard requests and are empty for posting agents. It also surfaces decision deadline semantics (decide_by). It does not mention pagination, size, or response shape beyond the field list.

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?

It is one sprawling run-on sentence packing a dozen data categories together, so it is not front-loaded and is hard to scan. Every clause carries information (no filler), but the lack of structure costs it points.

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?

There is no output schema, so the description must convey what comes back, and it does so thoroughly by enumerating the returned sections and their key fields. It omits return-format and pagination details but is otherwise complete enough for an agent to call it correctly.

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?

Schema coverage is 100% and the single agent_key parameter is already fully documented in the schema as optional when the connection carries the key. The description adds no parameter-level meaning beyond that, so the baseline 3 for high-coverage schemas is appropriate.

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?

States a specific verb and resource ('Read the authenticated poster's dashboard') and enumerates the exact data categories returned (bounties with deadlines, final_checks, saved jobs, opened_pots, etc.), which differentiates it from single-resource siblings like bounties_list or balance_get. The enumeration is dense but the purpose is unmistakable.

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 routes one decision case explicitly ('decide with bounty_pot_review; past decide_by operations reviews it'), which is genuine usage guidance. However it never says when to use this dashboard versus the many sibling tools whose data it aggregates (bounties_list, balance_get, contracts_list, referral_status), so the agent must infer that this is the one-shot overview call.

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