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

With no annotations provided, the description carries the full burden. It discloses that it requires an authenticated user and returns a list of followed podcasts, implying a read-only operation. However, it does not mention any additional behavioral details such as pagination, ordering, rate limits, or authentication failure handling. The description is minimally 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, concise sentence that front-loads the core action and resource. There is no extraneous information, and every word contributes to understanding the tool's purpose.

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 tool's simplicity (no parameters, no output schema), the description is adequately complete. It specifies the resource and user scope, which is sufficient for a straightforward getter. It could be enhanced by describing the return format, but for a list-returning tool, the current description covers the essential context.

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 tool has zero parameters, so there are no parameters to explain. The description adds no parameter semantics beyond the schema because the schema is empty. Per the rubric, 0 params baseline is 4; the description is consistent with that.

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 tool's function: 'Get the list of podcasts the authenticated user follows on AudioAlpha.' It uses a specific verb ('Get'), identifies the resource ('list of podcasts'), and specifies the scope (authenticated user's follows on AudioAlpha). This distinguishes it from siblings like get_my_favorite_assets and get_podcast_episodes.

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 usage when you need the authenticated user's followed/favorite podcasts, but provides no explicit guidance on when to use this tool over alternatives or any exclusions. No alternative tools are mentioned, and the context is inferred from the name and description.

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