get_track_freeze_status

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

With no annotations, the description takes on the behavioral disclosure burden. It explicitly notes that freezing/flattening cannot be triggered via the API, marking this as a read-only status check. It also clarifies that the tool returns two boolean values (frozen status and freezability). This adds meaningful context beyond the basic function name.

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 concise, front-loaded with the primary purpose, and structured into clear sections (Args, Returns, Note). Every sentence provides necessary information without redundancy or clutter.

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?

The description covers the essential aspects: purpose, parameter semantics, return values, and a key limitation (read-only API). Since an output schema exists, further return value detail is not necessary. It is sufficiently complete for a simple getter 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?

The input schema provides no description for track_index, so the description fills the gap by stating 'Zero-based index of the track.' It also explains the return semantics, which helps the agent understand both input and output meaning.

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 states the verb ('Get') and resource ('freeze status of a track'), then further specifies the return values ('whether the track is frozen and whether it can be frozen'). This distinguishes it from other track-related tools like get_track_info.

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 does not provide explicit guidance on when to use this tool versus alternatives. There is no mention of preferred context, exclusions, or alternative getters. The read-only note gives some context but does not directly address tool selection.

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