batch_enable_disable

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

Annotations indicate readOnlyHint=false and destructiveHint=false, matching the description's mention of enable/disable (mutation but not destructive). The description adds scope context but does not disclose permissions, side effects, or error conditions beyond what annotations imply.

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 concise sentence that front-loads the action, resource, and scope. No unnecessary words, highly efficient.

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 batch operation with 4 parameters and no output schema, the description covers the basic function but lacks details on conditional parameter requirements (e.g., track_type/track_index for 'track' target), return values, or success/failure indicators. Adequate but not comprehensive.

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 baseline is 3. The description reiterates the target scope but does not add significant meaning for parameters like track_type or track_index, which have conditional requirements (required when target='track') not clarified in the description.

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 action (enable/disable), the resource (multiple clips), and the scope (selected, track, or all). It is specific and distinguishes from the sibling tool 'enable_disable_clip' which operates on a single clip.

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 for batch operations but does not explicitly state when to use this tool versus alternatives like 'enable_disable_clip' for single clips. No prerequisites or exclusions are mentioned, though context is clear.

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