Fetch an ABC News Australia author profile from a canonical URL to retrieve byline metadata, biography, and recent articles.
Get an ABC News Australia author profile. Returns an ABC News Australia author's byline metadata, biography, and recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical ABC News Australia author 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 itself must convey behavior. It does disclose the type of data returned (metadata, biography, recent articles), which is useful for a read-only fetch. It does not mention limits, pagination, failure modes, or output structure, but for a simple fetch tool this is adequate.
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?
A single sentence that front-loads the action, states the target resource, and summarizes the return value. Every clause earns its place with no filler or repetition.
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 one-parameter, read-oriented lookup, the description covers the input, the domain, and the expected return content. It could be slightly stronger on output shape or how to recognize a canonical URL, but nothing essential is missing for invoking the tool correctly.
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 sole parameter is already described as a canonical ABC News Australia author URL. The description only repeats that same concept without adding format, examples, or how to obtain the URL, so it provides no significant extra parameter meaning.
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 and resource: 'Get an ABC News Australia author profile.' It further enumerates what is returned (byline metadata, biography, recent articles), making the tool's function unmistakable and distinct from article/section/headline siblings.
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 author URL' gives a clear input requirement, implying the tool should be used when an author URL is available. However, it does not explicitly contrast this with alternatives like abcau_article or other author tools, so routing guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.