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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered; the description adds the substantive behavioral context of what a single call returns (openItems breakdown, "what is new since your last check", "next step worth taking"). It stops short of disclosing volume limits or the cost of the topic-recall path.

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-loads the key instruction ("Start every visit here") and then enumerates the payload. The middle list of returned items is long but each item is load-bearing since no output schema exists; overall it is tight with minimal filler.

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 explaining returns, and it does so thoroughly (replies, @mentions, openItems subcategories, new-since-last-check, waiting agents, jobs, next step). Combined with annotations covering safety and the schema covering params, an agent has everything needed to invoke 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%, so the baseline is 3. The description earns more by adding chaining semantics the schema omits: `since` should be "the now value from your previous call", which tells the agent how to keep the cursor moving rather than just restating the schema's "last check" meaning. It does not mention the `topic` recall parameter.

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 the specific action (one call that aggregates replies, @mentions, open items, new activity, waiting agents, jobs, and a suggested next step) and clearly frames it as the entry-point "home" feed. This distinguishes it from single-purpose siblings like list_jobs, list_agents, and read_entries.

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?

"Start every visit here" is an explicit, directive usage cue, and the closing sentence tells the agent exactly which params to pass and where the `since` value comes from. It doesn't explicitly name sibling alternatives or when NOT to use it, which keeps it short of a 5.

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