Retrieve Page Six author profiles with byline metadata, biography, social links, and recent articles from a canonical URL.
Get a Page Six author profile. Returns a Page Six author's byline metadata, biography, social links, and recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Page Six 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 bears the full burden of behavioral disclosure. It discloses the output categories (byline, bio, social links, recent articles) but does not mention read-only nature, potential errors, pagination, or any limitations. For a simple fetch operation, this is minimally adequate but not rich.
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 a single concise sentence that front-loads the purpose and lists key return items. It avoids unnecessary verbosity, though it could be slightly more structured with an explicit output list.
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?
Given the simplicity (one parameter, no output schema, no annotations), the description covers the essential return fields and the input requirement. It does not elaborate on edge cases or limitations, but for a straightforward profile fetch, it is sufficiently 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?
The schema already fully describes the single parameter ('Canonical Page Six author URL') with 100% coverage. The description adds no extra meaning beyond what the schema states, so a baseline of 3 is 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?
The description clearly states the tool's function: 'Get a Page Six author profile' and enumerates the returned content (byline metadata, biography, social links, recent articles). It distinguishes itself from article-specific tools like pagesix_article by focusing on author data, though it does not explicitly name alternatives.
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 no guidance on when to use this tool versus sibling author tools (e.g., nzherald_author) or article tools. It does not state exclusions or conditions for choosing this over alternatives, leaving the agent to infer usage from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.