Fetch GhanaWeb section headlines and return article cards for a chosen section such as news, sports, or business.
Get GhanaWeb section headlines. Returns article cards from a verified GhanaWeb section page.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Section slug from ghanaweb-sections |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full behavioral burden. It states the output is article cards but doesn't disclose pagination, freshness/recency, rate limits, or whether the section must be an exact enum match. Minimal 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?
Two short sentences, front-loaded with the action and result. Efficient, though the second sentence is slightly redundant with the first.
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 annotations means the description should explain more about the returned article cards (fields, count, ordering) and when to use this over sibling news tools. It is under-specified for a tool in such a dense sibling cluster.
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% and the enum fully documents the section parameter. The description mentions 'section page' but adds no format or selection guidance beyond the schema. 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?
States a specific verb (Get) and resource (GhanaWeb section headlines), and the second sentence clarifies the return unit (article cards). However, it does not differentiate from sibling tools like ghanaweb_news or ghanaweb_sections, which is a missed opportunity given the crowded headline-tool namespace.
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 ghanaweb_news, ghanaweb_sections, or ghanaweb_article. The description says 'verified GhanaWeb section page' but doesn't explain what a verified section is or when to pick this over related siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.