Fetch a public SBS News author profile with name, image, biography, pagination state, and recent articles from a canonical byline collection URL.
Get an SBS News author profile. Returns a public SBS News byline collection with author name, profile image, biography, pagination state, and recent articles.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical SBS News author collection URL | |
| page | No | 1-based author archive page number |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It usefully states the collection is public and enumerates return fields, but does not explicitly state read-only behavior, rate limits, or absence of side effects.
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 the purpose front-loaded followed by return details. No filler; each clause contributes useful information.
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 simple two-parameter read tool with no output schema and no annotations, the description covers purpose and return shape sufficiently for invocation. It could add usage routing and explicit read-only/safety context, but is largely complete.
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%, so both url and page are fully documented in the input schema. The description adds no parameter meaning beyond that, making the baseline score of 3 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 ('SBS News author profile'), and names the source so it is distinguishable from sibling tools such as sbsnews_article and sbsnews_headlines. The purpose is clear and specific.
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 explicit when-to-use guidance, exclusions, or alternatives are given. The agent can infer it retrieves an author profile, but nothing routes it against sibling author/article tools or states prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.