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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context: the download link is short-lived, and it notes that MCP approval requirements are configurable by the organization administrator while business workflow approvals always apply. This goes beyond the annotations and informs the agent about potential approval gating. It does not cover rate limits or error conditions, but for a read-only operation this is sufficient.

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?

The description is three sentences and reasonably concise, but the first sentence ('Use this when working with RetailHardHat invoices records in the connected organization') is generic filler that delays the core action. The actual purpose is front-loaded in the second sentence. The approval note is relevant but could be merged for better flow.

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?

The tool has an output schema and detailed annotations, so the description needn't explain return values or safety. It adds approval context but lacks usage guidance (when to choose this tool) and parameter semantics beyond the schema. For a single-parameter read tool, this is adequate but leaves clear gaps that could confuse an agent about when and how to invoke it.

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 0% — the single parameter invoiceId has no description in the schema, only a UUID format and pattern. The tool description does not mention the parameter at all, so it fails to compensate for the low schema coverage. The agent must infer that invoiceId refers to a specific invoice identifier, which is not explicitly stated.

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 clearly states the verb 'Get' and the resource 'short-lived download link for an invoice attachment', which is specific and distinguishable from sibling tools like list_invoices or get_invoice_approval_request. However, it does not explicitly name any sibling or clarify why one would choose this over related invoice tools, leaving a small gap.

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 opening sentence 'Use this when working with RetailHardHat invoices records in the connected organization' is too broad to guide tool selection. It does not indicate when to use this tool versus list_invoices, get_invoice_approval_request, or other invoice-related siblings. No exclusions or alternative suggestions are provided.

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