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

Annotations already declare destructiveHint=false, readOnlyHint=false and openWorldHint=false, so the safety profile is covered; the description adds real value by explicitly bounding the scope ('never publishes, opens a social network, or authenticates'), which confirms the closed-world posture in plain language. It stops short of describing the side effect of 'attaching' — where the image lands or whether it mutates scene/project state, consistent with readOnlyHint=false.

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, zero padding: the first delivers purpose, the second delivers the scope boundary. Front-loaded and every clause 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?

With no output schema, the one real gap is what the caller gets back — an image handle, a file path, an attachment reference — which 'attach' implies but never specifies. Otherwise complete for a two-optional-parameter tool whose annotations already cover mutation safety.

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 both parameters (width, height) carry their own constraints (1280–4096, 720–4096) in the schema. The description adds nothing about sizing defaults, aspect expectations, or branding behavior, so the schema does all the work — baseline 3.

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?

Specific verb pair (prepare/attach) plus a precise resource: a branded PNG of the current Blender 3D viewport. It implicitly separates itself from take_screenshot and render_project_image via the 'branded' qualifier, but never names those siblings, so the differentiation is left to inference.

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?

States a clear triggering condition: use only for an explicitly requested share or export workflow. That excludes casual screenshotting, but no alternative tool is named for the non-share case, so the agent must guess that take_screenshot covers ad-hoc captures.

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