export_develop_preset

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

No annotations are provided, so the description carries the full burden. It discloses the operation is an export (read-like) but doesn't mention whether it overwrites files, what happens if the preset is missing, or whether it requires specific permissions. The word 'exact' hints at precision but lacks behavioral 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?

The description is a single, focused sentence with no filler. It front-loads the action and resource, though it could add a brief note about parameter usage without becoming verbose.

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 6 parameters, 0% schema coverage, no annotations, and an output schema present, the description is too sparse. It doesn't explain how to specify which preset to export, what the output schema contains, or edge cases. The presence of an output schema reduces the need to describe return values, but the input side remains under-specified.

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 0%, so the description must compensate, but it doesn't explain any of the 6 parameters. The description only mentions 'custom or plugin-managed Develop preset' without clarifying how preset_name, preset_uuid, preset_scope, preset_folder, or filename relate to identifying the preset or the output file.

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 states a specific verb ('Export') and resource ('Develop preset backing file'), and clarifies it exports 'one exact' preset, distinguishing it from bulk export or listing operations. It doesn't explicitly name sibling tools, but the phrase 'custom or plugin-managed' and 'backing file' adds specificity.

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?

No guidance on when to use this tool versus alternatives like get_develop_preset or list_develop_presets. The description implies usage for exporting a preset file, but doesn't state prerequisites (e.g., preset must exist, how to identify it) or exclusions.

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