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

With no annotations, the description carries the burden of behavioral disclosure. It discloses that the tool uses oEmbed, implying a read-only external API call. The term 'Meta' suggests a metadata lookup, which hints at non-destructive behavior. However, it does not explicitly state read-only status, rate limits, or whether input must be a URL, leaving some ambiguity.

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 with no filler. It front-loads the purpose and uses a compact notation ('Track/user title + author') to convey output structure. Every word contributes meaning, and it is appropriately sized for a simple lookup tool.

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?

Despite the tool's simplicity and the presence of an output schema, the description is incomplete because the only parameter is undocumented. An agent cannot determine how to query for a track or user without knowing whether 'q' expects a URL, a name, or an ID. The lack of input guidance makes the tool unusable without external knowledge, and the description does not compensate.

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 one optional parameter 'q' with no description (0% coverage), and the description does not explain what 'q' should contain. The parameter name 'q' is generic and could refer to a query, URL, or identifier. The description focuses on output fields (title, author) but not input semantics, leaving the agent to guess how to construct a valid request.

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 clearly identifies the resource (SoundCloud) and the output (track/user title + author) via oEmbed. It implies a 'fetch metadata' operation, though it lacks an explicit verb. The mention of oEmbed distinctly frames it as a metadata lookup tool, setting it apart from siblings like youtube or vimeo by naming the platform, though it does not directly compare to them.

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 provides no guidance on when to use this tool versus alternatives. With siblings like youtube and vimeo, an agent has no information about the intended use cases, such as 'when you need SoundCloud metadata' or exclusions like 'for YouTube use youtube'. No context or conditions are mentioned.

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