get_canvas

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

Discloses authentication requirement (needs SPOTIFY_SP_DC), which is a behavioral trait. However, no annotations exist, and description does not state read-only nature, rate limits, or other behavioral details.

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?

One sentence, very concise. But lacks necessary details, making it under-informative rather than efficiently complete.

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?

Despite having an output schema, description is minimal. Lacks explanation of what Canvas is, return format, or error conditions, leaving the agent underinformed for a simple 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?

Single parameter 'value' has no description in schema (0% coverage) and description adds no meaning. Does not clarify that 'value' is likely a track ID.

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?

Clearly states verb 'Fetch' and resource 'track's Canvas looping video', distinguishing it from sibling tools like get_track. Adds prerequisite 'needs SPOTIFY_SP_DC'. Could be more specific about what 'Canvas' is.

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?

Mentions authentication requirement ('needs SPOTIFY_SP_DC'), implying usage context. No explicit guidance on when to use this tool vs alternatives like get_track or get_track_visuals.

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