Get the 8 core ABC News sections accepted by abcnews-headlines. Use this section inventory to select valid categories before fetching news headlines.
Get ABC News sections. Returns the ABC News section inventory: the 8 core news sections accepted by abcnews-headlines.
| 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 burden, and it states what the call returns and the fixed scope (8 core sections). It doesn't discuss side effects, but for a zero-parameter list operation, no destructive or permission behavior needs flagging.
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 short sentences, with the core action front-loaded and the integration detail in the second sentence. Every word adds value.
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 inventory tool, the description fully equips an agent to call it and interpret the result's role. The reference to abcnews-headlines closes the main integration question.
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?
There are no parameters, so the schema is empty; the description adds the useful semantic detail that the returned values are valid section inputs for abcnews-headlines. Baseline 4 applies because no parameter documentation is needed.
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 exact resource ('ABC News sections'), and explains the output ('section inventory' with the 8 core sections). It also ties the result to abcnews-headlines, which separates it from sibling article/headline/news tools.
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 statement that these are 'the 8 core news sections accepted by abcnews-headlines' clearly frames the tool as the source of valid section values for that sibling. It does not explicitly exclude other tools, but the contextual relationship is enough for an agent to know when to call it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.