Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds a concrete behavioral limit beyond the structured data: the profile returns exactly the 15 most recent stories, which signals result scoping and implicitly that older work requires another tool.

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?

A single tight sentence with the key noun-resource phrase front-loaded and no filler. Every clause carries information about what the profile contains.

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?

An output schema exists, so return values need no extra explanation, but two undocumented, both-optional identifier parameters with no guidance on selection is a real gap for a lookup tool. Nothing states the accepted identifier format or what happens if neither is supplied.

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 0% and the description never mentions the two parameters. An agent is left to guess whether the author is identified by `url`, by `slug`, or by either, and both are optional with no stated requirement.

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?

"One Raw Story author's public profile" names a specific resource and scope, and the follow-on clause enumerates the returned fields (name, bio, avatar, social links, 15 recent stories). It is clearly distinguishable from siblings like rawstory_article and rawstory_news, though it never states what identifies an author for lookup.

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 gives no when-to-use guidance and never mentions the sibling tools. It also fails to say when to prefer this author profile over rawstory_article or rawstory_headlines, leaving routing entirely to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.