Get my likes

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent understands it's a safe read operation. The description adds the scope (logged-in user's likes) but does not disclose pagination behavior or ordering. Without annotations, this would be lower.

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, which is concise but missing important details like pagination. It is not overly verbose, but it could be more informative without being long.

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 two parameters with no output schema, the description is incomplete. It does not mention that the result is a paginated list or how to use nextPage. Annotations provide safety context but the description lacks functional completeness.

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 0%, and the description does not explain either parameter (limit, nextPage). The agent must infer from parameter names only; 'nextPage' is ambiguous. The description adds no value for parameter semantics.

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 retrieves the logged-in user's liked tracks. The verb 'Get' and resource 'liked tracks' are specific, and it distinguishes from sibling tools like 'like_track' or 'get_track'.

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 on when to use this tool vs alternatives like 'get_track' or 'search_tracks'. It does not mention prerequisites or that it only works for the authenticated user, though the title implies it.

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