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

No annotations exist, so the description carries the full burden. It usefully discloses the nature of the returned artifact (a Designer file, editable step-by-step, runnable as-is in the App), but says nothing about whether the call is read-only, whether it produces or mutates anything, or what happens when the name doesn't match a protocol.

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 short sentences, front-loaded with what the caller receives and followed by the two actionable things to do with it. Nothing is padded, though the opening clause is slightly elliptical.

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?

With no output schema, the description is the only source of truth about the return value, and it identifies the format but not how the file is delivered (path, base64, downloadable URL) or how large/complex it is. Combined with the undocumented 'name' parameter for a tool whose whole job is fetching an artifact, meaningful gaps remain.

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?

There is a single required 'name' parameter with 0% schema description coverage, and the description adds no explicit meaning for it. However, for a one-parameter retrieval tool the surrounding sentences make the context clear enough that the gap is minor rather than blocking.

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 the resource produced: 'The protocol as an Opentrons Protocol Designer file', which implicitly contrasts with the plain-protocol sibling get_protocol. The verb is only implied by the tool name ('get'), but the artifact and its format are unambiguous.

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?

Usage is implied rather than stated: import it at designer.opentrons.com to edit without code, or run it in the Opentrons App. It never explicitly says when to pick this over get_protocol or which of the two to request for a given task, so the agent must infer the choice from the format difference.

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