Fetch a Dawn author's public profile and recent articles from a canonical author URL, returning their name, biography, and published work as structured JSON.
Get a Dawn author profile. Returns one Dawn byline's public profile (name and biography, when Dawn publishes one) and their recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical www.dawn.com/authors/<id>/<slug> 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 carries the disclosure burden. It is transparent about the conditional biography ('when Dawn publishes one') and that recent articles are included, which adds behavioral context. It does not mention response formatting, empty results, or rate limits, but for a simple read-style tool this is acceptable.
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 compound sentence that front-loads the tool's purpose and packs in the key output details without filler. It could be split into two sentences for readability, but 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 one-parameter tool with no output schema, the description covers the input type, the returned profile fields, recent articles, and the notable edge case of a missing biography. Extra details like article count or pagination would be nice but are not essential for invoking the tool correctly.
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%: the single 'url' parameter already specifies the canonical www.dawn.com/authors/<id>/<slug> format. The description only adds the generic phrase 'canonical author URL' and provides no meaningful semantic value beyond the schema, so baseline 3 applies.
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 Dawn author profile') and explicitly enumerates the returned content: name, biography, and recent articles. It differentiates from Dawn article/news tools by focusing on the byline, though it does not directly contrast with other author-profile 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: call this when you need a Dawn author's public profile and recent articles from an author URL. It does not explicitly say when to prefer this over alternatives or when not to use it, leaving the agent to infer selection from the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.