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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: the output is step-by-step UI instructions (screens, buttons, fields) and the tool 'opens nothing by itself', which is the single most important thing an agent needs to know before calling. It stops short of describing the shape or length of that returned guidance.

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 front-loaded clause 'from ChatGPT, Claude or any AI agent' is filler, and the closing sentence about ConnectWise's REST API and the absence of a documented MCP server (with a checked-on date) contributes nothing to calling the tool. The one operationally important fact — that it returns instructions and performs no action — is buried mid-sentence rather than stated first.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so only at a high level ('step by step (screens, buttons, fields)'). It does not indicate how the guidance should be consumed or whether the ConnectWise app must already be connected, leaving gaps for a guidance-style tool.

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 object, so there is nothing for the description to disambiguate. Baseline for a parameterless tool is 4, and nothing in the description misrepresents the input surface.

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 eventually states that the tool 'Returns how to do it in ConnectWise step by step (screens, buttons, fields) and opens nothing by itself', which is a procedural-guidance behavior. However, the opening clause 'Read ticket notes in the user's own ConnectWise account' and the name connectwise_read_ticket_notes set up the expectation that actual note content is returned, so an agent must read the whole description to learn it only gets instructions. The purpose is recoverable but muddled by the read-vs-guide framing.

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 one explicit sequencing rule: this tool does nothing itself, so follow it with the cotlet_browser_* tools in the Cloud Browser. That is useful routing guidance. It does not say when to prefer this over sibling guidance tools such as cotlet_app_guide, nor when the browser route is unnecessary or inappropriate.

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