get_track

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

With no annotations, the description carries the behavioral burden, and it does disclose the return payload (analysis data, timed segments, prose reviews, YouTube URLs) plus the semantic that segments are synced to audio. It omits read-only nature, error behavior for a bad slug, and any auth or rate-limit context, so it is adequate but incomplete.

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?

Front-loaded purpose sentence followed by a compact enumeration of contents and an Args block; every line carries information. Only minor redundancy in restating the slug source in both the description and the Args note.

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?

Since an output schema exists, the description needn't re-explain return values, and the single parameter's origin is covered. Missing only edge-case behavior (slug not found) and explicit read-only confirmation, which are minor for a one-parameter getter.

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 coverage is 0% (the schema only labels the field 'Slug'), so the description must compensate — and it does, giving both the source (list_tracks) and a concrete format example ('pink-sky-at-night'). That is real added meaning beyond the 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?

States a specific verb and resource ('Get the full manifest for a track by slug') and enumerates what the manifest contains, so the agent knows what it will receive. It doesn't explicitly differentiate itself from sibling get_analysis or search_reviews, which is the only reason it isn't a 5.

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 gives one genuine usage hint — the slug comes from list_tracks, with a concrete example. However, it never says when to prefer this over get_analysis or search_reviews, which are obvious alternatives given the shared track/review domain.

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