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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the aggregate nature of the result, the state filter ('transcript in, not yet turned into pages'), and that approval cards are scoped to the caller. Pagination/limits are not mentioned, keeping it below a 5.

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?

Front-loads the three inbox categories before the routing sentence, so the agent gets the core scope first. The colon-list and semicolon-chained next-moves sentence are dense but every clause carries information; no filler.

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?

There is no output schema, so the description must describe what comes back, and it does: the three item categories and their pending states. Combined with annotations covering safety and the schema covering the sole parameter, an agent has enough to call it 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?

Schema description coverage is 100% and there is a single optional workspace parameter, so the schema fully documents it. The description adds nothing about the workspace parameter (e.g., how it affects which inbox items appear), so the baseline 3 applies.

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?

States a specific verb (list) and a precisely scoped resource (the Compass Inbox) and enumerates the three categories it aggregates: finished interviews awaiting review, AI-proposed opportunities awaiting accept/dismiss, and the caller's pending approval cards. This distinguishes it from the narrower siblings compass_interviews_list and compass_opportunities_list without the agent needing to open either schema.

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?

Explicitly positions itself as 'THE place to answer what needs me?' and gives concrete next moves that route to compass_interviews_get/compass_pages_create and compass_opportunities_accept/delete. It lacks an explicit when-not (e.g., pointing to compass_opportunities_list for a full unfiltered list), so it stops short of full alternative coverage.

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