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 the genuinely non-obvious behavioral fact that it 'opens nothing by itself' and returns a procedure, which explains why a tool named 'add private note' is read-only. It does not describe the shape of the returned steps or any dependencies on the user's Chatwoot plan or role.

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 operative content is two sentences, but they are padded: 'from ChatGPT, Claude or any AI agent' adds nothing, and the closing sentence about Chatwoot's REST API and lack of an official MCP server is meta-justification that does not help an agent select or invoke the tool. The most important fact (it opens nothing and only returns a how-to) sits mid-description rather than up front.

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 guidance tool with annotations covering safety and no output schema, the definition covers purpose and downstream handoff adequately. It leaves open what the returned procedure looks like, how granular it is, and what the agent should do if the steps do not match the user's UI. Those gaps are real but modest.

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 and the schema is an empty closed object, so there is no parameter meaning left to convey. Baseline for a parameterless tool applies. The description correctly avoids inventing parameter talk.

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 description names a specific resource (a private note in the user's own Chatwoot account) and, critically, clarifies the actual deliverable: step-by-step instructions with screens, buttons, and fields rather than the action itself. That clarification rescues an opening sentence that would otherwise read like a mutation. It also distinguishes itself from the cotlet_browser_* tools that perform the action, though it does not differentiate itself from cotlet_app_guide or chatwoot_reply_to_conversation.

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?

Usage is implied through a workflow: call this to get instructions, then execute with the cotlet_browser_* tools in the Chatwoot Cloud Browser. However, there is no explicit when-to-use versus when-not-to-use, no statement about when to skip this tool (e.g., the agent already knows the flow), and no prerequisite checks such as whether a browser session must already be open.

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