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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful content-level context — it lists exactly which fields the profile exposes, including the side effect of returning the author's recent articles. It does not, however, say how an author is identified or whether url and slug are alternatives.

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 efficient sentence with no filler, front-loading the resource and then the payload. It is well-sized for a lookup tool, though it omits any usable operational detail in that brevity.

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-value documentation is not required. The remaining gap is input identification: two undocumented, optional identifier parameters with zero schema coverage leaves the agent guessing how to target a specific author.

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 (url, slug). It only implies that some author identifier is needed. With both params optional and undocumented, an agent has no guidance on which to supply or whether they are interchangeable, so the description fails to compensate for the coverage gap.

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 names a specific resource (a Rappler author's public profile) and enumerates its contents: name, bio, social links, and recent articles. That is concrete enough for an agent to know what comes back. It stops short of differentiating itself from sibling tools like rappler_article or rappler_headlines, which share the same news-site prefix.

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, no prerequisites, and no mention of alternatives (e.g., use rappler_article for article content, rappler_author for the writer profile). The agent must infer the routing decision entirely from the name.

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