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

The description adds useful behavioral detail beyond annotations: it checks all activity sources in parallel and requires no action-specific parameters. The readOnlyHint and destructiveHint annotations already establish safety, and the description does not contradict 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 concise and front-loaded: the first sentence captures the full purpose, and the action bullet is short and useful. 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?

Given the simple check-only action, read-only annotations, and complete input schema, the description provides enough context for an agent to invoke the tool correctly. It lists what the dashboard contains, though it could be slightly more explicit about the output structure or time window.

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 baseline is 3. The description adds the useful clarification that the 'check' action requires no params, but it does not expand on org_uid or other parameter semantics 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 clearly states the tool's purpose: getting a consolidated overview of proposals, pending offers, messages, and contract updates in one call. This distinguishes it from more granular sibling tools like list_client_proposals, get_messages, list_offers, and list_contracts.

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 'all in one call' phrasing implies this tool is for when a broad, consolidated snapshot is needed rather than individual detail calls. However, it does not explicitly name alternatives or state when not to use it, leaving the agent to infer routing.

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