Retrieve an RTÉ News author profile from a canonical URL, including byline, role, headshot, and recent articles.
Get an RTÉ News author profile. Returns an RTÉ News author's byline name, role, headshot and recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical RTÉ 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 provided, the description carries the full burden of behavioral disclosure. It makes the read-only nature clear via 'Get' and describes the expected output, but does not mention failure behavior, canonical URL requirements beyond the schema, availability limits, or any other operational traits.
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 no filler. The primary action and output are front-loaded, and every phrase contributes to understanding the tool's purpose.
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 one-parameter tool with no output schema or annotations, the description adequately covers what the tool needs and what it returns. It lists the key output components, though it could add minor detail about the format or scope of 'recent articles'.
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%, so the schema already documents the single 'url' parameter as a 'Canonical RTÉ author URL'. The description adds little beyond repeating that same phrase, so it does not improve parameter understanding.
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 ('RTÉ News author profile'), and enumerates the returned fields: byline name, role, headshot, and recent articles. This clearly distinguishes it from sibling tools like rte_article, rte_news, and rte_headlines, which target different resources.
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 implies the tool is for retrieving an author profile from a canonical author URL, but it does not explicitly state when to prefer it over alternatives or provide exclusion criteria. No sibling comparison or when-not-to-use guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.