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

Annotations already declare readOnlyHint, idempotentHint and non-destructive; the description adds real context beyond them by stating that it 'opens nothing by itself' and that the return is procedural (screens, buttons, fields). It does not state prerequisites such as the Cloud Browser session needing to be signed in to Instapaper, which would matter before the follow-up browser calls.

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?

Front-loading is poor: the misleading 'Move to folder' action claim comes first and is only corrected in the second clause. The closing sentence about Instapaper's REST API v2 and the absence of an official MCP server, complete with a 'checked 17 Oct 2026' date, does nothing to help tool selection, and 'from ChatGPT, Claude or any AI agent' is filler.

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?

For a zero-parameter, read-only guidance tool with no output schema, the description conveys the essential shape of the return (step-by-step screens, buttons, fields) and the handoff to browser tools. It omits authentication/prerequisite state and does not say how much of the procedure comes back (single page vs. full flow), which an agent needs to plan the follow-up.

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 tool takes zero parameters, which is the baseline-4 case. The description implicitly justifies the empty schema by explaining that the tool only produces instructions and leaves the article/folder choice to the subsequent cotlet_browser_* interaction.

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 clause 'Move to folder in the user's own Instapaper account' reads as an action, but the follow-up 'Returns how to do it in Instapaper step by step ... and opens nothing by itself' reveals the tool is a guidance/instruction generator. The actual function is stated, but the name, title and first clause all point the agent at a mutation it will not perform, so the agent must read two sentences to learn what it really does.

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 gives an explicit workflow division: use this to get the step-by-step procedure, then execute it with the cotlet_browser_* tools in the user's Instapaper Cloud Browser. That routes the agent away from expecting this tool to act. It stops short of naming when a sibling such as instapaper_archive_article would be preferred instead.

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