genius_get_song

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

With no annotations provided, the description must disclose behavioral traits but only states 'Get a Genius song by ID.' It does not mention authentication needs, rate limits, data mutability, error handling, or response format. The agent has no information about side effects or constraints.

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 extremely concise (one sentence) but sacrifices essential information. It is not appropriately sized; it omits crucial context that should be present for a tool with no annotations or output schema. Conciseness is not a substitute for completeness here.

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 lack of annotations, no output schema, and only 0% schema description coverage, the description is severely incomplete. It does not explain return values, error conditions, or provide any context about what constitutes a valid request or response.

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 schema has 0% description coverage for both parameters (id and api_key). The description only says 'by ID', which maps to the 'id' parameter but does not explain what the ID represents, its format, or the purpose of api_key. The description adds minimal meaning beyond the schema structure.

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 it gets a Genius song by ID, which is specific and uses a verb+resource format. However, it does not differentiate from sibling tools like genius_artist_songs or genius_search, leaving some ambiguity about scope.

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 provided on when to use this tool versus alternatives like genius_search or genius_artist_songs. There are no when-to-use or when-not-to-use instructions, leaving the agent without decision-making context.

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