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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds scope context ('across all programmes') and the aggregation framing, but leaves open whose items are returned ('the person' vs the authenticated caller) and says nothing about ordering, grouping, or empty results. Useful additive context, but modest beyond what structured fields already 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?

Two sentences: an enumeration of contents followed by an actionable 'start here' directive, with the routing advice placed last where it is most salient. The item enumeration is long but each element earns its place by telling the agent what will come back.

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 zero parameters, a rich annotation set, and an output schema that documents the return shape, the description only needs to establish purpose, scope, and when to call. It does all three. The remaining gap is the identity/aggregation semantics (whose items, and whether results are grouped per programme).

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 the baseline applies and there is no parameter meaning for the description to supply. The description correctly signals that no filtering input is expected by framing the call as a single 'everything waiting' query.

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?

The description enumerates the concrete item types returned (upcoming meetings, forms, match requests, programme to-do lists, surveys, mentoring tools, events) and scopes them as 'everything waiting for the person across all programmes', which clearly separates it from single-collection siblings like list_tasks or list_meetings. It stops short of naming an explicit contrast tool, so it is clear but not maximally differentiated.

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 here when the person asks what to do next' gives an explicit entry-point trigger, which is exactly the routing signal an agent needs among 21 siblings. There is no when-not-to-use clause, e.g. pointing to list_next_steps or list_tasks for narrower/structured queries, so the guidance is strong but one-sided.

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