Export Document

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the tool modifies a file but does not destroy the original. The description adds that it exports the active document without mentioning further behavioral aspects (e.g., whether the file is overwritten, if any dialog appears). It does not contradict annotations.

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 extremely concise: two sentences with no redundancy. The first sentence states the core purpose, the second provides key details on formats and requirements. Every sentence 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?

Given the tool's simplicity (4 parameters, conditional options, no output schema), the description covers the essentials. However, it lacks information on default behavior for omitted optional parameters, overwrite semantics, or whether the export is at full resolution. Still adequate for a standard export function.

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 the schema already documents each parameter. The description adds value by summarizing that scale is for PNG only and quality for JPEG only, and stresses that the path must be absolute. This enhances understanding 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?

The description clearly states the verb 'Exports', resource 'active document', and lists supported formats (PNG, JPEG, PSD, TIFF) with additional options like scaling for PNG and quality for JPEG. It is specific and distinguishes from sibling tools like ps_save_document.

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 instructs to provide an absolute file path and mentions conditional parameters, but it does not explicitly state when to use this tool versus alternatives like ps_save_document or ps_batch. No when-not-to-use guidance is given.

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