Fetch a Denver Post author archive by slug or profile URL to get the public bio and first-page articles.
Get a Denver Post author archive. Returns one author's public profile and the articles listed on its first page.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Canonical denverpost.com/author/<slug>/ URL; alternative to slug | |
| slug | No | Author slug, e.g. aldo-svaldi |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It does disclose useful behavior: the return is a public profile plus only the first page of articles, which warns of pagination limits. It says nothing about auth, rate limits, or error behavior, so it is only partially transparent.
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 tight sentences with the core action front-loaded and the return scope immediately following. No filler or redundancy.
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?
With no output schema, describing the returned payload (profile plus first-page articles) is genuinely useful and largely sufficient for calling the tool. The remaining gap is the lack of routing guidance among the many sibling author/news tools.
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%, with both url and slug documented as alternatives, so baseline is 3. The description adds no syntax or format detail beyond what the schema already provides.
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 and resource ('Get a Denver Post author archive') and clarifies the scope as one author's public profile plus articles from its first page. An agent can distinguish it from denverpost_article by the 'author archive' framing, though it never names siblings explicitly.
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 guidance on when to use this over denverpost_article, denverpost_news, or denverpost_headlines, and no prerequisites for obtaining a slug. Usage is only implied by the tool name itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.