Fetches fresh headlines from a chosen Billboard section so you can monitor music, charts, awards, or industry news in clean JSON.
Get Billboard section headlines. Returns fresh headlines from one public Billboard section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Billboard section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Returns fresh headlines' without detailing the response format, pagination, error handling, or any constraints. It doesn't disclose what happens with invalid sections, rate limits, or the structure of returned data. This is a significant gap for a tool with no annotations.
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 fluff. The action is front-loaded and the scoping (one section) is mentioned early. Efficient and clear, though it could add a bit more detail without bloating.
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?
The tool is simple (one parameter, no output schema), but the description is incomplete for agent use. It doesn't describe what the returned headlines look like (fields, links, timestamps), nor does it mention any limitations or error scenarios. Without an output schema, the agent needs more context about what to expect, which 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?
Schema description coverage is 100%, so the baseline is 3. The description adds minimal meaning by saying 'one public Billboard section', but this is largely redundant with the schema's 'Billboard section slug'. It doesn't explain the parameter further, so it stays at the baseline.
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 action (get headlines) and the resource (Billboard section). It specifies 'section headlines' and 'one public Billboard section', which distinguishes it from general news or article tools. However, it doesn't explicitly contrast with sibling tools like billboard_news or billboard_sections, but the purpose is 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over billboard_news, billboard_article, or other headline tools. No explicit exclusions or alternatives are given, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.