get_task

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

With no annotations provided, the description carries the behavioral disclosure burden. It does indicate a read-only fetch and what is returned, but it omits important async behavior such as eventual consistency, polling, and whether the result payload is empty until the task completes. This is useful but incomplete.

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 a single front-loaded sentence with no filler. The key action and resource appear immediately, and every word adds meaningful information.

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 low-complexity tool with two fully-documented required parameters, the description plus schema covers the essentials for invocation. The only notable gap is the missing async/polling context, but that is minor for selecting and calling the tool correctly.

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?

Schema description coverage is 100%, so the schema already fully documents task_id and action, including the action enum. The description adds no additional meaning or format detail beyond 'suno task', so the baseline score of 3 is appropriate.

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 names a specific verb ('Fetch'), a clear resource ('a suno task'), and the exact data returned ('current status and latest result payload'). It is immediately distinguishable from the sibling tools, which are all task-creation endpoints like convert_audio, cover_audio, and text_to_music.

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?

There is no when-to-use or when-not-to-use guidance. The description does not say to call this after submitting an async task, to poll until completion, or how it relates to the creation endpoints. Usage must be inferred entirely from the verb 'Fetch' and the sibling tool names.

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