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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the operation writes to disk or returns data, what authentication or credits it consumes, whether it is idempotent, or what errors are possible. 'Export' implies a mutation/side effect but this is never clarified.

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?

Extremely short, but here brevity reflects under-specification rather than efficiency. There is only a four-word fragment with no structure to speak of.

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 tool with three required parameters, no annotations, and no output schema, the description supplies essentially nothing about inputs, behavior, or results. It is wholly inadequate for correct invocation.

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?

Three required parameters (source_key, instrument, kwargs) with 0% schema description coverage and no explanation in the description. The opaque 'kwargs' string parameter is particularly undocumented, leaving the caller unable to construct a valid call.

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 'AI MIDI Export' essentially restates the tool name export_midi and adds only the vague qualifier 'AI'. It does not specify what is being exported from, what format or content the MIDI contains, or how it differs from siblings like extract_chords or extract_single_instrument.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent has no basis for choosing this over the other twelve siblings.

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