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

Annotations already declare read-only behavior, and the description adds useful behavioral context beyond that: results are ordered soonest first, scoped to the active Space, and a loop leaves the list once the manager reports on it. It does not cover pagination or detailed return shape, but the key lifecycle behavior is disclosed.

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 short and front-loads the core concept, ordering, and scoping. It is generally efficient, though it repeats the read-only annotation and restates active-Space scoping in both the first and last sentences.

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 one fully documented parameter, a read-only annotation, and no output schema, the description gives enough context to call the tool correctly and understand the rough return: each change and when, soonest first. Minor omissions like pagination or exact response fields are acceptable for a simple list operation.

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 description coverage is 100%, so the single space_id parameter is already fully documented in the schema. The description mentions passing space_id as an override for this call, but adds no syntax or semantic detail beyond what the schema already provides.

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 states a specific resource and scope: open promises/loops for the active Space, ordered soonest first, with each change and its timing. It is clear enough to distinguish this from generic list tools, though it does not explicitly name a sibling alternative beyond set_active_space for switching context.

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?

Usage is implied by the concept of open promises and the lifecycle note that loops disappear once reported on. The description explains how to change or override the active Space, but it does not say when to use this tool versus related siblings such as get_latest_briefing or get_sync_status.

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