list_export_presets

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

Without annotations, the description provides useful behavioral details: it scans disk, includes built-in presets, and doesn't require Adobe Media Encoder. This gives the agent context beyond the basic 'list' operation, though it doesn't describe return format or error behavior.

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 clear sentences front-load the main purpose and add a practical usage tip. No redundant wording.

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?

The tool is simple, and the description covers the core purpose, a key environmental fact (AME not needed), and the connection to export_sequence. Optional parameters are documented in the schema.

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?

The schema already describes the 'filter' parameter, and 'limit' is self-explanatory from its constraints. The tool description adds no additional parameter semantics, so it doesn't exceed the baseline for 50% coverage.

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 'List Adobe .epr export presets on disk' which identifies the exact resource and action. The added detail about including Premiere-shipped presets and referencing export_sequence further clarifies its distinct role among siblings.

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 implies usage in the export workflow by saying 'Pass the path of one to export_sequence,' indicating when this tool is needed. However, it doesn't explicitly name alternatives or exclusions, so it falls short of fully explicit guidelines.

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