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

Annotations declare destructiveHint=true and non-idempotent, and the description adds real operational context the annotations don't: the 10 MB decoded limit and the auth flow (without a signed-in Printdash account the connection prompts sign-in on printdash.io). It does not say whether attaching replaces or removes existing artwork, which is exactly what destructiveHint=true implies – that is the one missing piece.

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 audience restriction, then payload mechanics, then auth, with nothing padded. Slightly dense for two-and-a-half sentences, but each clause carries a distinct constraint.

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 a full output schema and 100% input coverage, the description only needs to add the non-schema facts, and it supplies the two critical ones: size limit and auth requirement. The remaining gap is the destructiveness semantics of an artwork attach.

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 target/file_name/data_base64 are already fully documented including side, design and kind enums. The description only restates the extension requirement on file_name and the 10 MB ceiling on data_base64, adding little beyond the schema.

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 and resource ('attaches a file sent as base64 in data_base64') and scopes it to programmatic clients, immediately separating it from attach_artwork, attach_artwork_from_url and get_artwork_uploader_link. An agent can route between them without opening a 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?

Explicit when-to-use (programmatic clients, inline base64 up to 10 MB, same target/file_name signature as attach_artwork) and explicit when-not ('Never paste a file a customer dropped into a chat here'), with the two named alternatives to use instead. No inference required.

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