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 disclosure (returns a profile plus recent articles), but says nothing about pagination, whether email is always present, or lookup failure behavior. With annotations doing the safety work, a 3 is appropriate.

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 front-loaded sentence with no filler; the field list is efficient. It is appropriately sized for a simple profile lookup.

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 not be explained. However, for a lookup tool whose two optional identifier parameters are undocumented, the description leaves the core invocation question (which parameter, what format) unanswered.

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?

Both parameters (url, slug) have 0% schema description coverage and the description never mentions how to identify an author. It does not explain that either a URL or a slug can be supplied, nor whether one is preferred or required (both are optional). The description fails to compensate for the schema 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 states a specific resource ('One Mediaite author's public profile') and enumerates the returned fields (name, biography, avatar, email, X/Twitter links, recent articles). It is clearly distinct from the article/headlines/news/sections siblings by resource type, though it does not explicitly name those siblings for contrast.

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 routing to alternatives such as mediaite_article. The agent gets no guidance on how it fits alongside the other Mediaite tools.

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