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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the output is 'bounded' (implying size limits), it is a review artifact, and it includes 'source extraction issues'. It also clarifies the output is base64 bytes, which is a behavioral detail beyond the schema. No contradiction with annotations.

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?

Two sentences with no filler. The core action and output format are front-loaded, and the review-artifact caveat is placed immediately after. Every sentence earns its place.

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-parameter read-only export tool with rich annotations and no output schema, the description is nearly complete. It explains what the output is, how to handle it, and what it includes. The only minor gap is that it doesn't describe the workbook's structure or how the base64 bytes should be decoded, but the instruction to use client tools mitigates that.

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%, so the schema already documents the only parameter (projectId) with a clear description. The tool description doesn't add parameter-level detail beyond the schema, but it does reinforce that projectId is a Helvabase project/mapping ID. Baseline 3 is appropriate because the schema carries the parameter semantics fully.

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 ('Return'), a specific resource ('current traceability matrix'), and a specific format ('bounded XLSX review workbook (base64 bytes)'). It also distinguishes itself from approval/submission exports, which helps differentiate it from sibling export tools like helvabase_export_dossier and helvabase_export_document_pack.

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?

The description clearly indicates this is a review artifact and explicitly says it is 'never an approval or a submission export', which tells the agent when not to use it. It also instructs to save and open it using client tools. However, it doesn't explicitly name alternative tools or provide a when-to-use vs. when-not-to-use comparison beyond the approval/submission distinction.

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