get_task

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. It does disclose the payload semantics ('current status and latest result payload'), implying a non-mutating poll that may return partial results, but it says nothing about blocking behavior, rate limits, or what status values or error states can come back.

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 tight sentence with no filler, and the core purpose is front-loaded in the first few words. Nothing needs trimming.

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?

With no output schema and no annotations, the description is the only source for return and behavioral semantics. It names what comes back (status plus latest result payload) but omits status value semantics, pending/failed handling, and polling expectations for a tool that spans 15 asynchronous endpoints.

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%: both task_id and action are documented, including the 15-value action enum described as the async endpoint the task was created on. The description adds no additional meaning about how to supply or interpret these parameters, so the baseline 3 applies.

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 gives a specific verb and resource ('Fetch the current status and latest result payload for a suno task'), which clearly separates it from the generation-oriented siblings like text_to_music or cover_audio. It stops short of naming an alternative or stating explicitly that it is the polling counterpart to those async endpoints, so it is clear but not sibling-disambiguating at a 5 level.

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?

Usage is only implied: a reader infers this is the tool to poll after submitting an async job, since 'for a suno task' plus the enum of async endpoints hints at the workflow. There is no explicit when-to-use statement, no polling cadence or retry advice, and no note on what to do while a task is still pending.

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