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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely useful behavioral context with no output schema: what the payload contains (metadata plus the actual transcript) and that downstream typing/splitting rules live in the compass skill.

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?

Three short sentences, front-loaded with what the tool returns before the usage advice. The clause about the compass skill's typing/splitting rules is slightly tangential but still earns its place by explaining why the transcript matters.

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?

For a single-resource read with full schema coverage, covered annotations and no output schema, the description supplies what an agent needs: the return content, the id source, and the workflow context. It does not address failure modes (unknown id, missing workspace) but little more is required here.

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%, so the baseline would be 3. The description goes slightly beyond the schema by naming compass_inbox_list as an additional source of interviewId, which the schema's own description does not mention. It says nothing about the workspace parameter, so this is a modest lift, not a full one.

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?

Opens with a specific verb and resource: fetch one interview in full, including metadata and transcript. It is immediately distinguishable from compass_interviews_list (plural enumeration) and from the create/revoke siblings that mutate interview state.

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?

States the trigger condition explicitly ('read this before summarizing an interview or drafting pages from it') and tells the agent where the required id comes from (compass_interviews_list or compass_inbox_list). That is concrete routing guidance rather than implied usage.

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