Fetch a ScienceAlert journalist's public profile, biography, social links, and recent articles using the author listing URL.
Get a ScienceAlert author profile. Returns a journalist's public profile, biography, social links, and one page of recent articles.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical ScienceAlert author listing URL, e.g. /michelle-starr/page/0 |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It usefully discloses the response shape (profile, biography, social links) and flags a limitation ('one page of recent articles'), implying results are truncated and paginated. It does not mention auth, rate limits, or how to fetch additional pages, so it only partially covers behavior.
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 no filler, front-loaded with the primary action and then the return contents. Every clause carries information an agent can use.
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 single-parameter read tool with no output schema, the description adequately covers both what it does and what comes back. Missing are pagination mechanics (how to move past the 'one page') and any prerequisites, which would be needed for full completeness.
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% for the single `url` parameter, and the schema already supplies the example URI format. The description adds nothing about the URL beyond what the schema documents, so the baseline of 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 ScienceAlert author profile') and the second sentence enumerates the returned content, which goes beyond the name. The site prefix distinguishes it from other *_author siblings, but it does not explicitly distinguish itself from sciencealert_article or the other ScienceAlert 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?
There is no statement of when to use this tool, when not to, or which sibling to prefer instead. An agent gets no routing guidance between this and sciencealert_article/headlines.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.