suno_get_task_status

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

No annotations are provided, so the description carries the behavioral burden. It does disclose that the call returns status and audio URLs, which implies a read-only polling operation, but it does not cover what happens for pending tasks, invalid task IDs, or whether repeat calls are safe.

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?

A single, front-loaded sentence with no filler. Every word contributes to identifying the operation, the resource, and the expected return payload.

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 one-parameter status retrieval tool, the description names the main return data and is largely sufficient for correct invocation. It would be more complete with explicit guidance about post-generation usage or behavior when the task is still processing, but those are not essential for a basic call.

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 schema has no property descriptions and schema description coverage is 0%, but the single parameter taskId is self-explanatory given the tool name and description. The description does not add meaning beyond the parameter name, but the gap is minor because there is only one required parameter.

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 ('Get'), the resource ('current status'), and the key output ('generated audio URLs') for a Kie.ai Suno task. This clearly distinguishes the tool from the sibling suno_generate_music, whose purpose is creation rather than retrieval.

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 the tool should be used after a task exists, since it fetches status and results for an already-created task. However, it does not explicitly say 'use after suno_generate_music' or explain when polling is appropriate, leaving the usage context to inference.

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