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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds that it returns progress and listening links and that it requires a connected Starchild member, which is useful extra context not in annotations. However, it does not describe polling behavior, rate limits, or what happens if the job is not found or expired.

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 concise sentence that is front-loaded with the key context (Starchild member, progress and listening links). It is efficient and wastes no words, though it could be slightly more informative without being verbose.

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 read-only status-check tool with one required parameter, the description is incomplete. It fails to explain the 'job' parameter, does not cover prerequisite (connected member is mentioned but not elaborated), and lacks details on what 'progress' means or how to interpret the listening links. Without an output schema, the description should do more to set expectations.

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 0% and the single parameter 'job' has no description in the schema. The tool description does not explain what 'job' represents, its format, or where to obtain it. This is a significant gap because the parameter is required and undocumented.

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 that it returns progress and listening links for a transform, which gives some idea of the resource. However, 'Check my new version' in the title is ambiguous, and the description does not explicitly say it checks the status of an existing transform started by transform_song; it implies it by referencing the sibling tool. Without the sibling reference, the purpose would be unclear.

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 mentions that it is for a connected Starchild member and references a transform started with transform_song, but it does not provide explicit when-to-use guidance such as 'use this after calling transform_song to poll for completion' or when not to use it. There is no comparison to alternatives.

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