batch_convert

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 reveals the underlying process (using -j flag) and the base64 encoding requirement, but does not disclose side effects, error handling, authentication needs, or performance implications.

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 concise (5 lines) and well-structured: first line states purpose, then bullet points for job requirements, then return behavior. No unnecessary words, but could be slightly more compact without losing clarity.

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 existence of an output schema (not shown), the description appropriately omits return value details beyond ordering. It covers input structure well but might benefit from mentioning error handling or concurrency limits for a batch tool.

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 input schema provides no descriptions for parameters (0% coverage), but the description compensates by listing the required keys (in_b64, in_suffix, out_format) with types and examples, adding critical semantic meaning 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 'Convert multiple score files in a single MuseScore process using -j' clearly states the verb (convert), resource (multiple score files), and the specific flag used. It distinguishes itself from the sibling 'convert_score' which likely handles single conversions.

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 specifies the required fields for each job dict (in_b64, in_suffix, out_format) and notes that results are returned in order. However, it does not explicitly explain when to use batch_convert over convert_score or other alternatives, leaving some ambiguity.

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