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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the call returns a screen-by-screen procedure and performs no navigation or opening itself, which tells the agent this is a planning step, not a data fetch.

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?

The essential facts are front-loaded, but the second sentence is an overstuffed semicolon chain mixing the return value, the no-side-effect guarantee, and the follow-up tool family. The closing sentence about Instapaper's REST API v2 and the absence of an official MCP server, including a dated audit stamp, does nothing to help an agent decide or invoke this call.

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?

With no parameters and no output schema, the description carries the burden of describing the return value, and it only gestures at 'how to do it step by step (screens, buttons, fields)' without indicating structure, granularity, or failure modes. It is adequate to attempt a call but leaves the agent guessing what it will actually receive back.

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?

The schema has zero parameters, so there is no parameter meaning to add; baseline 4 applies. The description correctly implies no inputs are needed by describing the call as taking no arguments and returning a procedure for later execution.

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 first sentence names a specific verb and resource ('List unread articles') and scopes it to 'the user's own Instapaper account', which separates it from write-oriented siblings like instapaper_save_url or instapaper_archive_article. The second sentence muddies the action model by revealing that the tool returns a step-by-step procedure rather than the articles, leaving the agent to reconcile 'list articles' with 'return instructions'.

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?

It does say what to do next ('then do it with the cotlet_browser_* tools in the user's Instapaper Cloud Browser') and rules out autonomous execution ('opens nothing by itself'), which is useful routing. But it never states when to choose this over instapaper_fetch_article_text, cotlet_app_guide, or the other Instapaper siblings, so selection remains inferential.

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