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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds valuable semantics the annotations cannot: the exact composition of the inbox, that fillIn is excluded from total, and that offsetting cards are pending approvals. It does not describe pagination or ordering, so not 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-loaded with the core purpose in the first clause, then sub-lists, then next moves. It is dense and long, but every section earns its place; the routing guidance and owner-lead instructions are not padding.

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, and the description compensates by naming the three inbox categories, the uncounted fillIn set, and the recommended follow-up tools for each category. Missing only explicit pagination/ordering and what a total counts, which is minor for a read-only overview tool.

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 coverage is 100% and the single workspace parameter is fully documented, so the baseline is high. The description adds no parameter detail but does not need to, and it clarifies the return shape and the fillIn/total relationship which supports interpretation of results.

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 exactly what is returned: finished interviews awaiting review, AI-proposed opportunities awaiting accept/dismiss, and pending approval cards, plus the fillIn sub-list. This is a specific verb+resource and distinguishes itself from siblings like compass_opportunities_list and compass_interviews_list by framing all of them as a decision queue.

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 says it is 'THE place to answer what needs me?' and names concrete follow-up alternatives (compass_interviews_get → compass_pages_create, compass_opportunities_accept/delete, compass_links_create with kind owns/part_of). It even states a when-not/guardrail: 'never guess an owner'.

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