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 one useful trait beyond them: the call 'opens nothing by itself' and returns textual instructions rather than article data. The remaining sentences about Instapaper's REST API v2 and the absence of an official MCP server are background rationale, not behavior an agent needs in order to invoke the 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?

The text is padded with marketing framing ('from ChatGPT, Claude or any AI agent') and a dated aside about API v2 and MCP server availability ('checked 17 Oct 2026') that does nothing to help invoke the tool. The essential fact — that this returns step-by-step guidance and is followed by cotlet_browser_* calls — is buried in the middle rather than front-loaded.

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, no output schema, and full annotation coverage, the definition gets the workflow across (returns guidance, then act via cotlet_browser_*). What is missing is a clear statement of what the returned guide contains and what the agent should do with it next, plus any tie-break against the other instapaper_* tools; the ambiguous 'fetch' framing leaves the agent guessing about the response shape.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; per the baseline for 0-param tools this lands at 4. No parameter claims conflict with the empty schema.

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 opening sentence says 'Fetch article text in the user's own Instapaper account', which matches the name and title, but the second sentence reverses that into 'Returns how to do it in Instapaper step by step ... and opens nothing by itself'. An agent reading only the first clause would expect article content and instead receive instructions. The actual purpose (a how-to guide) is stated, but only after a misleading lead.

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 give a concrete next step — 'then do it with the cotlet_browser_* tools in the user's Instapaper Cloud Browser' — which is genuine routing guidance. However, it offers no guidance on when to use this versus the plain Instapaper siblings (instapaper_read_highlights, instapaper_list_unread_articles), nor any condition under which this tool should be skipped in favor of direct API-backed calls.

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