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

With no annotations, the description carries the behavioral burden and discloses useful context: the summary is private and limited to authorized projects, it shows attention categories, pagination/truncation flags matter, and planning readiness is not execution permission. It does not detail authentication or rate-limit behavior, but it goes well beyond the schema.

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 front-loaded and compact at four sentences, with no obvious padding. Some terms are dense, but each sentence contributes scope, result interpretation guidance, or a caveat.

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 no annotations, no output schema, and low schema description coverage, the description is fairly complete: it explains what is included, which fields to inspect, and what the result does not represent. The main remaining gap is precise page-parameter semantics.

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 0%, so the description must compensate. It mentions 'per page' and 'next_page', giving pagination context for the single optional page parameter, but it does not explain page numbering, defaults, or constraints beyond what the schema already shows.

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 verb and resource: read a private work-attention summary across authorized projects, and it names the attention categories shown. It is clear what the tool does, though it does not explicitly distinguish itself from sibling inbox tools like get_board_inbox or check_agent_commons_inbox.

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?

It gives result-handling guidance: follow next_page and inspect truncated, source_limit_reached and unavailable_projects before treating an empty result as complete. However, it does not say when to choose this tool over the many sibling inbox and execution tools, leaving tool selection mostly implied.

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