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

'Look up' implies a read-only retrieval, and the note about new generation being unavailable adds meaningful context beyond the tool name. However, since there are no annotations, the description does not clarify what the tool returns, error behavior, or access prerequisites, leaving notable gaps.

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 very concise—two short sentences, both conveying essential information with no filler. The first sentence front-loads the core action, and the second adds an important context note.

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 lookup-by-id tool, the description gives the minimum viable information. But with no annotations and no output schema, it would help to state what a returned job represents or the fact that this only retrieves job metadata rather than sound assets.

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 description mentions job_id but adds little meaning beyond the schema property name. With 0% schema_description_coverage, the description should compensate by explaining the format, source, or semantics of job_id, but it only restates that the lookup happens 'by job_id.'

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 that the tool looks up a historical generation job by job_id, which is specific and action-oriented. It does not explicitly distinguish itself from sibling tools like get_sound, but the focus on 'generation job' makes the tool's purpose reasonably 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 phrase 'New generation is no longer available' hints that this tool is for existing/historical jobs only, but it does not explain when to use this tool versus alternatives such as get_sound or get_role_sound. No exclusions or decision guidance is provided.

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