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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces rather than contradicts them by stating the tool "opens nothing by itself" and only returns instructions. It also discloses the prerequisite that execution happens inside the user's Patreon Cloud Browser session. It stops short of saying what the returned payload looks like or whether it accounts for account-specific state, which is a minor gap given no output schema.

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-loaded with the core mechanic and the handoff to the browser tools, then a compact justification about the API limitation. The phrase "from ChatGPT, Claude or any AI agent" is filler that earns no place, and the parenthetical date check adds length for marginal value.

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, non-executing helper tool, the description covers purpose, what is returned, what is not done, the follow-up tool family, and why the direct-API path is unavailable. No output schema is needed because the shape of the answer (step-by-step screens, buttons, fields) is described inline.

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?

Zero parameters, so the empty object schema is fully self-explanatory and the description correctly spends no words on parameter semantics. Baseline applies since there is nothing to disambiguate.

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 ("Create post in the user's own Patreon account") and immediately clarifies the actual mechanic: it "Returns how to do it in Patreon step by step (screens, buttons, fields) and opens nothing by itself." That single clause prevents the obvious misread of the tool name and separates it from the sibling create-capable browser tools.

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?

Explicit when-to-use and what-to-do-next: call this first, then "do it with the cotlet_browser_* tools in the user's Patreon Cloud Browser." It also pre-empts the natural alternative (Patreon's official API v2) and explains why that route does not work for post creation.

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