list_available_audio_transitions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'lists' without clarifying that it is a read-only operation, what the return format is (e.g., list of names), or whether any project context is required. It fails to explicitly state non-destructive behavior or output shape, leaving the agent to infer safety.

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, clear sentence with no redundant words. It is appropriately concise for a zero-parameter list operation, front-loading the core action and resource without fluff.

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?

For a simple list tool, the description is mostly adequate, but the absence of an output schema means it should ideally state what is returned (e.g., transition names or objects) and whether any project must be open. It also doesn't note that the operation is non-destructive. These minor omissions leave slight ambiguity for an agent.

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?

With zero parameters, the input schema is fully covered (vacuously) and there is nothing to document. The baseline of 4 applies because there is no semantic gap to fill; the description correctly adds no parameter details since none exist.

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 'Lists all available audio transitions in Premiere Pro' clearly states the specific verb 'list' and the resource 'audio transitions'. It naturally distinguishes itself from siblings like list_available_transitions (which may include video) and list_available_audio_effects, making the tool's purpose unambiguous.

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 gives no explicit guidance on when to use this tool versus alternatives. The name implies use when audio transitions are needed, but no exclusions or alternative routes (e.g., list_available_transitions for combined transitions) are mentioned. This is an implied usage only.

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