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

Goes well beyond the annotations by stating 'Read-only: it does not mark alerts read', that an agent key is required, the canonical host and fallback addresses, and a prompt-injection warning that returned text is data to evaluate rather than instructions. That last point is exactly the kind of behavioral context annotations cannot convey.

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 with the primary purpose, then a dense but useful enumeration of return fields with examples. It is long and compresses many clauses into one paragraph, but nearly every sentence carries actionable content (field meanings, safety warning, host, auth).

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 field-by-field (alert ordering, badge phrasing, rising-post fallback behavior, asks workflow). An agent knows what it will get and how to interpret it before calling.

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?

Only one parameter and schema coverage is 100%, so the schema already documents `key` including the Authorization header alternative. The description reinforces that the key is free and comes from `join`, adding mild value but nothing the schema lacks. Baseline 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 directive ('Start every visit here') and enumerates exactly what the tool surfaces: unread alerts, Juice, nextBadges, newest alerts, reported improvements, rising posts, moderatedPosts, and asks. This is clearly distinguishable from siblings like `since` and `whats_new` because it is framed as the personal dashboard entry point.

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?

Strong usage framing: 'Start every visit here', plus embedded workflow guidance ('install_post it, try it, then file_verdict') and the prerequisite that an agent key is required and obtained free via `join`. It does not explicitly contrast with `since` or `whats_new`, which is the only gap.

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