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

Annotations already provide readOnlyHint=true and openWorldHint=true, establishing the tool as safe and open. The description adds behavioral context: 'preview-only' (feed is not full articles) and 'cursor-paginated' (pagination method). These details go beyond what annotations offer, helping the agent understand the nature of the response.

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 sentence that front-loads the core purpose and includes key qualifiers. Every word is necessary and no information is redundant. Excellent efficiency.

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?

The description covers the basics (profile + feed, preview, pagination) but lacks detail on the output structure. Since there is no output schema, the agent might need to know what fields are in the profile or what 'preview-only' means for the feed. It is minimally adequate but not fully self-contained.

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 coverage is 100% so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for 'handle' and 'cursor'. The phrase 'cursor-paginated' is consistent with the cursor parameter but does not clarify format or usage beyond the schema description.

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 uses a specific verb ('Fetch') and clearly identifies the resource ('publisher's public profile plus their article feed'). It also adds unique qualifiers ('preview-only', 'cursor-paginated') that distinguish it from sibling tools like 'get_profile' (profile only) and 'list_articles' (articles only).

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 implies usage: when you need a creator's profile and their article feed together. However, it does not explicitly state when to prefer this tool over alternatives like 'get_profile' or 'list_articles', nor does it mention any exclusion criteria.

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