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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the 15-minute link expiry and the required re-call pattern, plus the downstream user obligation to verify, sign and submit. It does not state whether the link is single-use or bound to the requesting user, which would be the remaining useful detail.

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 the core action before the expiry caveat and the user reminder. Each sentence carries information, though the reminder-to-user instruction is workflow guidance rather than tool semantics and could be seen as slightly out of scope.

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, so the description correctly characterizes the return as a link and warns about its lifetime. Combined with a single fully-specified parameter and a complete annotation set, an agent has what it needs to invoke this correctly; only the link's single-use/user-binding semantics are left unstated.

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% and the single artifact_id parameter is fully documented in the schema with format and pattern. The description only alludes to it indirectly via generate_filled_pdf, adding no syntax or sourcing detail beyond the schema. Baseline 3 applies.

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 (get) and resource (download link for a PDF) and ties the artifact's origin to a named sibling, generate_filled_pdf. An agent can distinguish this from generate_filled_pdf or get_application without opening any schema.

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 establishes the prerequisite (a PDF produced by generate_filled_pdf) and tells the agent what to do when the link lapses ('call again for a fresh one'). It stops short of explicit exclusions or naming an alternative tool for other artifact types, but the context is clear.

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