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

The description discloses the non-obvious behavior that matters most: the tool emits instructions rather than executing, and it opens nothing. That is consistent with readOnlyHint=true and destructiveHint=false. The trailing note about Printful's official REST API and absence of an official MCP server is contextually informative but not behavior the agent needs in order to call it.

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 middle sentence is efficient and carries the essential facts, but the closing sentence about the Printful REST API, private tokens and OAuth is tangential to invoking this tool and includes an oddly specific audit date. The most important fact (this returns a guide, it does not list anything) is not 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?

For a parameterless guide tool with no output schema, the description covers what is returned (screens, buttons, fields) and what it delegates to. It stops short of the workflow essentials an agent needs: whether a browser session must be opened first, and what to do if the returned steps do not match the live UI.

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, so there is no parameter meaning for the description to supply; the baseline applies. Nothing is misstated about inputs.

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 'List orders in the user's own Printful account' reads like a data-retrieval tool, which is misleading: the second sentence reveals the tool actually returns a step-by-step procedure and performs nothing itself. The real purpose is stated, but only after a misleading lead. An agent scanning the name and first sentence would expect orders in the response.

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 route the agent forward ('then do it with the cotlet_browser_* tools') and warns that it 'opens nothing by itself', which is useful. However, it never states when this tool should be preferred over cotlet_app_guide or a direct cotlet_browser_open/navigate call, and no prerequisite ordering (e.g. browser session must already be open) is given.

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