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

Annotations declare openWorldHint=true and readOnlyHint=false; the description adds real context on top of that — the invite is a no-account guest link, the transcript returns as reviewable draft pages, and the call may return needs_confirmation requiring a user pause. It does not cover auth or rate-limit behavior, but the confirmation and side-effect profile is well disclosed.

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 definition, then the usage rule, then the closing procedure. Dense but nearly every clause carries information; the final sentence is a slightly compressed run-on covering needs_confirmation and the user hand-off, but it is 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?

For a 6-param tool with no output schema, the description covers the important return behavior (needs_confirmation pause) and the downstream outcome (draft pages), and pairs naturally with approvalId in the schema. Enough for an agent to invoke and handle the response 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?

Even though schema coverage is 100% (baseline 3), the description adds guidance the schema lacks: focusPrompt should name SPECIFIC gaps and cite the eval run id, and interviewee should be the workflow owner when the map knows one. This meaningfully shapes how an agent fills the parameters rather than restating them.

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+resource ('mints a stakeholder-interview invite') and describes the concrete artifact produced: a no-account guest link, an interviewer agent briefed by focusPrompt, and a transcript flowing back as draft pages. It is clearly distinguishable from sibling compass_interview_invite, which is referenced as the send step rather than the mint step.

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 names when to use this over the obvious alternative: when caliper_flow_performance shows failures clustered on missing company facts, 'the fix is usually not a prompt edit — it's asking the human who actually knows.' It also prescribes the operational sequence (name gaps with eval run id, pick the workflow owner, hand over the link) and the needs_confirmation handling.

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