Fetch an NBC News author's byline metadata and recent articles from their canonical URL, returning job title, bio, social links, and article list.
Get an NBC News author profile. Returns an NBC News author's byline metadata (job title, bio, social links) and their recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical NBC 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, the description carries the transparency burden. It correctly indicates a read-style operation and names the returned data, but it does not disclose pagination for the recent articles, error behavior for invalid/non-canonical URLs, or rate limits.
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 no filler; the verb and resource are front-loaded, and each clause adds meaning. It is appropriately compact for the tool's simplicity.
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 tool with no output schema, this is largely complete: it states the required input and the expected return categories. It stops short of specifying article count/pagination or failure modes, but nothing essential to a first correct call is missing.
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 schema already documents the single 'url' parameter with 100% coverage. The description repeats the 'canonical author URL' idea but adds no extra format, examples, or constraints 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 and resource ('Get an NBC News author profile') and enumerates the concrete output: byline metadata (job title, bio, social links) plus recent articles. This clearly differentiates it from sibling article/news/headlines tools.
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 intended use is implied by the return payload: an agent needing an author's byline or recent articles can infer this is the right tool. However, it never names alternatives or says when not to use it, leaving the guidance implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.