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

With readOnlyHint and idempotentHint already trueched, the description adds extra behavioral context by noting the single-call naturechers and by warning that 'figures in one group apply only to that group'. It also states the result includes counts and ages. This meaningfully supplements the annotations without contradicting them.

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?

The description is compact and front-loaded: the purpose and content appear in the first sentence, followed by direct use-case guidanceeto, an explicit exclusion of separate searches, and a necessary caveat. Every sentence earns its place without 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?

The tool is conceptually an aggregation of many result groups, and the description lists those groups clearly. The output schema covers return structure, and annotations cover safety, so the missing clarification of the 'scope' parameter is the main gap. Given the available schema and annotation context, the description is otherwise sufficient for an agent to call the tool 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?

The description says nothing about the two parameters. The schema documents 'days' (window and default), but 'scope' has only an enum and its semantics are not explained. With schema description coverage at 50%, the description does not compensate for the undocumented param, and 'user's' could even mislead about the effect of scope=workspace.

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 uses a specific verb ('Returns') with a clear resource ('the user's prioritised operational picture in one call'), then enumerates the exact categories included. It is self-evidently distinct from the sibling search/record tools, which do one type of lookup rather than this multi-group aggregate.

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?

The description gives explicit use-case phrases ('what needs my attention', 'what should I do today', 'what am I waiting on') and explicitly advises against rebuilding the same picture from separate searches. It does not name specific alternative tools or state when they should be used instead, so it stops short of full exclusion guidance.

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