shortest_saved_tracks

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

With no annotations, the description carries the full burden; it does disclose the read-only safety trait and the ascending sort order. However, it does not disclose that the ranking only covers tracks walked up to scan_cap (a potentially bounded subset of the library), nor how max_results truncates output, which are material behavioral traits for interpreting results.

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?

Two short front-loaded sentences with zero filler: the core action ('Rank your saved tracks by duration, shortest first') comes first, and the safety note ('Read-only') follows. Every word 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 a simple ranking tool with no annotations and no output schema, the purpose and safety profile are covered, but the scan_cap completeness caveat is omitted—an agent may not realize results can be a partial ranking over a bounded walk. No sibling routing is included either, though parameters themselves are well documented in the schema.

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 100%, so the baseline is 3. The schema already documents scan_cap, max_results, and response_format with defaults and enums, so the description's silence on parameters is acceptable.

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 ('Rank'), a precise resource ('your saved tracks'), and an exact sort criterion ('by duration, shortest first'). This clearly distinguishes it from its direct counterpart longest_saved_tracks without needing to open any schema.

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 is given about when to use this tool versus alternatives such as get_saved_tracks, search_saved_tracks, or the natural sibling longest_saved_tracks. With roughly 500 siblings, the absence of any when/when-not routing leaves the agent to infer usage solely from the name.

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