crompton_track

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

No annotations are provided, so the description carries full burden. It indicates a read operation ('Get metadata') with no side effects mentioned. However, it does not disclose any behavioral traits like idempotency, rate limits, or response structure beyond listing fields. The description is adequate but lacks depth.

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 sentence of 11 words, efficiently conveying the tool's purpose and key metadata fields. It is front-loaded and contains no superfluous information, earning full marks.

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 the simple input schema and no output schema, the description lists the included metadata fields, which is helpful. However, it does not explain 'available endpoints' or provide a complete picture of the return structure. Sibling tools suggest more specific alternatives, so the description could be slightly more comprehensive, but overall it is sufficient.

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 100% with a clear description of the track parameter (integer 1-13). The description adds no additional meaning beyond the schema; it does not elaborate on parameter format or provide examples. Baseline score of 3 is appropriate.

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 action (Get metadata) and the specific resource (a specific track), and lists the types of metadata included (title, theme, lead performers, audio stats, available endpoints). This distinguishes it from sibling tools like crompton_lyrics or crompton_waveform, which focus on individual aspects.

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 implies use for general track metadata, but does not explicitly state when to use this tool versus alternatives like crompton_lyrics for lyrics or crompton_waveform for waveform. No when-not-to-use or alternative suggestions are provided, so usage context is only implied.

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