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

With no annotations present, the description carries the full burden, and it does disclose the return format (base64-encoded MIDI data with metadata) and the 'completed' precondition. It omits other behavioral details such as behavior on incomplete jobs, permission/auth needs, or payload size characteristics.

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 tightly written sentences with zero filler: the first states the action and scope, the second states the return payload. The key information is front-loaded.

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 one-parameter tool with no output schema, the description supplies the return value detail (base64 MIDI plus metadata) that would otherwise be unknown, plus the completion precondition. It is close to complete, missing only error/failure behavior for incomplete jobs.

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 single job_id parameter has 100% schema description coverage including a format example (AIM-JOB-000001), so the schema does the heavy lifting. The description adds no syntax or semantic detail beyond implying the job must be completed, matching the baseline for fully documented schemas.

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 states a specific verb (Retrieve) and resource (raw MIDI artifact) and scopes it to a completed AImeistrO job. It does not explicitly differentiate from the sibling get_job, which also operates on a job_id, leaving some ambiguity about which to call for artifact vs. job metadata.

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 phrase 'for a completed AImeistrO job' implies the precondition that the job must have finished, which is useful routing context. However, it never explicitly states when to use this over get_job or what to do if the job is still running, so usage is only implied.

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