Raw SoundCloud API request

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

Annotations already communicate readOnly=false and openWorldHint=true. The description adds useful behavioral context: it uses stored credentials, returns raw JSON, and paginate=true adds linked_partitioning for a compact page. It could warn more about arbitrary POST/PUT/DELETE side effects, but 'call any endpoint' plus openWorldHint substantially covers that.

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?

Three sentences with no filler: the escape-hatch intent is front-loaded, the usage rule is stated clearly, and the return/pagination behavior is summarized efficiently. Every sentence earns its place.

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 an open-ended raw API client, the description covers purpose, when to use it, return format, and pagination behavior. It does not explicitly describe auth/account switching or error handling, but those are documented in the schema and sibling auth tools, so the core guidance is complete for an expert escape-hatch tool.

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 high (86%), so the parameter burden is mostly carried by the schema. The description adds little about individual parameters beyond what the schema already documents, such as the paginate behavior and stored credentials. This is adequate but not additive beyond the structured schema.

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 uses a specific verb ('call') and a clear resource ('any https://api.soundcloud.com endpoint'), and labels itself an 'escape hatch' for cases no dedicated tool covers. This strongly distinguishes it from the extensive list of specialized SoundCloud sibling tools.

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?

It explicitly states when to use the tool: only when no dedicated tool covers the need, and points to the skill's api-reference for the dedicated alternatives. This gives the agent a clear routing rule and an exclusion condition.

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