Retrieve the public Billboard section inventory, covering music, business, culture, media, Spanish-language categories, and Billboard Pro, each with its RSS feed link.
Get Billboard sections. Returns the public Billboard section inventory: every music, business, culture, media and Spanish-language category plus Billboard Pro, each linking to its public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description carries the behavioral disclosure burden. It does well by stating the data is public, enumerating the content categories, and disclosing that each section links to its RSS feed. It does not discuss output structure details, but this is a simple, read-only inventory fetch.
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?
Two sentences with no filler. The first sentence names the action and resource, and the second delivers the essential content details. Every clause earns its place.
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?
For a zero-parameter, no-output-schema tool, the description is complete: it tells the agent what will be returned, the scope of the inventory, and the notable RSS-feed linkage. Nothing needed for correct selection or invocation is missing.
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 the baseline is 4. The description correctly adds no parameter-related expectations and instead focuses on what will be returned, which is the appropriate behavior for a parameterless tool.
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 uses a specific verb ('Get'), names the resource ('Billboard sections'), and precisely defines the scope as the public section inventory: music, business, culture, media, Spanish-language categories, and Billboard Pro. This is distinct from sibling tools like billboard_article or billboard_headlines, making the tool's role immediately clear.
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 clearly implies when to use this tool: when you need Billboard's section inventory and RSS feed links. It does not explicitly name alternatives or state when not to use it, but for a zero-parameter catalog tool, the intended context is evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.