Fetches a Sky News author profile from a canonical URL, returning byline metadata, biography, and recent articles.
Get a Sky News author profile. Returns a Sky News author's byline metadata, biography, and recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Sky News author URL |
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 burden of behavioral disclosure. It states what is returned (byline metadata, biography, recent articles) and implies a read-only lookup via 'Get' and 'Returns', but it does not disclose potential failure modes, URL validation behavior, or how 'recent articles' are bounded. This is adequate but leaves some ambiguity.
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?
The description is two short sentences with the purpose front-loaded and no filler. The first sentence states the action, and the second details the return contents and required input format. Every sentence earns its place.
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, single-parameter read tool with no output schema and no annotations. The description covers what the tool does, what it returns, and what input is expected. Minor gaps exist around output structure and edge cases, but the description is sufficient for correct selection and invocation.
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?
The input schema already fully documents the single parameter as 'Canonical Sky News author URL' with 100% coverage. The description repeats this same concept ('canonical author URL') without adding additional meaning, so it provides no substantive value beyond the schema.
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 ('Sky News author profile'), and enumerates the returned content: byline metadata, biography, and recent articles. This clearly differentiates it from sibling tools like skynews_article or skynews_headlines by identifying it as the author-profile tool.
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 description provides clear context: use this when you need a Sky News author's profile, and pass a canonical author URL. It does not explicitly name alternatives or state when not to use the tool, but the resource type is distinct enough among the Sky News siblings that the intended usage is evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.