get_featured

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

No annotations provided; the description is minimal. It does not disclose how 'featured' is determined, whether authentication is needed, or any side effects. The agent lacks behavioral context.

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 very concise (2 words), but overly so. It lacks any structure, though it is not verbose. A single sentence would be more informative without harming conciseness.

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?

No output schema and no description of return value format. The agent cannot infer what data is returned (e.g., podcast IDs, full objects). For a simple retrieval tool, this is a notable gap.

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 descriptions for 'limit' and 'offset'. The tool description adds no extra parameter context, so baseline 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 name and description are specific: 'Get featured podcasts'. It clearly indicates retrieving a curated list, which is distinct from siblings like 'get_trending' or 'get_top_charts', though it does not explicitly differentiate.

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 versus alternatives. Siblings include other list-retrieval tools, but no context is given for when 'featured' is appropriate.

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