Fetch an Atlantic staff author's public profile, including name, headshot, biography, and recent articles, from a canonical author URL.
Get an Atlantic staff author profile. Returns one Atlantic staff author's public profile -- name, headshot, and biography -- plus their recent articles, from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical theatlantic.com/author/<slug>/ 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 must carry the behavioral burden. It indicates an idempotent read operation ('Returns') and that the profile is public, which suggests no auth, but it does not explicitly disclose side-effect-freeness, rate limits, or handling of authors with no articles. The mention of 'recent articles' adds some behavioral context without quantifying it.
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?
One sentence front-loads the core action and then specifies inputs and outputs with no filler. Every phrase 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?
For a simple one-parameter read tool, the description covers what it does, what it returns, and the required URL format. Minor gaps remain: no output schema, no sibling routing, and no detail on how many recent articles are returned, but these are not critical for basic 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 schema already documents the single parameter with 'Canonical theatlantic.com/author/<slug>/ URL' at 100% coverage. The description merely reinforces 'canonical author URL' without adding new format, examples, or edge-case guidance 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 states a specific verb and resource: 'Get an Atlantic staff author profile' and lists what is returned (name, headshot, biography, recent articles). It is clearly distinct from neighboring tools like theatlantic_article or theatlantic_headlines, but does not explicitly name them or contrast against them.
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 case—when an agent needs an Atlantic staff author's profile—is implied by the purpose statement, and the canonical author URL requirement is stated. However, it provides no explicit guidance on when to choose this tool over sibling tools such as theatlantic_article, theatlantic_headlines, or other publication author tools, and no exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.