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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: bearer-token auth, a nightly regeneration by tools/brief.py, and the fact that the content can lag the phone push — a staleness warning an agent cannot get from annotations or schema.

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?

Two sentences, both dense; the connector/scope and auth constraint are front-loaded before the content description. Slightly over-packed with provenance detail ('published with the next deploy'), but essentially no redundancy.

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?

An output schema exists, so return values need not be specified, and yet the description still sketches the payload shape. Together with auth, scope and freshness caveats, an agent has everything needed to call it correctly; only the relative-position vs sibling tools is unstated.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims are made that could mislead.

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 resource and enumerates its contents ('what was decided, what landed, and the items waiting on Joe, each as the task, why it matters and the steps'), which is well beyond a restated name. It does not explicitly distinguish itself from the sibling next_task_for_muse, whose scope ('next task') overlaps with 'items waiting on Joe', so it stops short of a 5.

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?

Names a real applicability gate ('For the referencesource Muse connector only') and an auth prerequisite (bearer token required), which tells the agent when it can be called at all. It never says when to prefer this over next_task_for_muse or message_supervisor, so the guidance stays implied rather than explicit.

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