Get track

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

Description is consistent with annotations readOnlyHint=true (it's a read operation) but adds no extra behavioral details beyond what the name implies. With annotations present, bar is lower; this is adequate but not enriching.

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?

One sentence, no wasted words. Perfectly concise 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?

Given low complexity, one required param, and annotations, the description is nearly complete. Lacks mention of return data but output schema is absent so not expected.

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 single parameter trackId is clear from schema (number, minimum 1), but description adds no explanation or context. With 0% schema description coverage, the burden is on description, which it fails to meet.

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?

Description clearly states verb 'get' and resource 'track'. Among siblings like get_comments, get_playlist, it uniquely identifies its function. No ambiguity.

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?

No guidance on when to use this vs other tools like get_playlist or get_user. No mention of prerequisites, context, or alternatives.

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