Fetch ABC News Australia article metadata and body paragraphs from a canonical article URL.
Get ABC News Australia article content. Returns public ABC News Australia article metadata and body paragraphs from a canonical article URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical ABC News Australia article URL |
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 burden of behavioral disclosure. It does disclose that the content is public and that the return includes metadata and body paragraphs, which is useful. However, it does not mention error behavior, rate limits, or what happens with non-canonical URLs, leaving some gaps.
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 no filler. The core action and output are front-loaded, and every sentence 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?
This is a simple one-parameter tool with no output schema or annotations. The description adequately covers what it does and what it returns, which is enough for an agent to use it correctly for a canonical article URL.
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% and the single parameter 'url' is already described as a canonical ABC News Australia article URL in the schema. The description adds no new parameter-level meaning beyond restating the same concept, so the baseline 3 applies.
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') and resource ('ABC News Australia article content') and clearly states that it returns metadata and body paragraphs from a canonical article URL. This distinguishes it from sibling tools like abcau_headlines or abcau_news, though it does not explicitly name them.
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 phrase 'from a canonical article URL' provides clear context for when to use this tool: when the agent has a specific article URL to fetch. It does not explicitly state when not to use it or name alternatives, but the condition is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.