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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the crucial non-obvious behavior that the tool "opens nothing by itself" and returns a guide rather than data, plus the note that Redbubble has no seller API or official MCP server — context an agent cannot get from annotations.

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-loads the purpose, then the return behavior, then the follow-up tool family, then the API caveat. The phrase "from ChatGPT, Claude or any AI agent" is mild filler, but the remaining sentences each carry real information.

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 guide tool with no output schema, the definition covers what comes back (step-by-step instructions), the handoff to browser tools, and why no direct API exists. Minor gaps remain — it does not say whether the user must already be logged in to the Cloud Browser.

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; baseline of 4 applies. The description correctly implies a parameterless, account-scoped call with no inputs to supply.

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?

States a specific verb and resource ("Get payment history in the user's own Redbubble account") and then clarifies what the tool actually returns: step-by-step screens, buttons, and fields rather than the data itself. That distinguishes it from the cotlet_browser_* action tools, though it does not explicitly contrast with sibling readers like redbubble_get_analytics.

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?

Gives explicit sequencing: this tool only produces instructions, then the agent must carry them out with cotlet_browser_* tools in the Cloud Browser. It does not name a when-not condition or any alternative route to payment history, but the usage path is unambiguous.

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