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

Beyond the readOnlyHint/idempotentHint annotations, it discloses that the tool 'opens nothing by itself', that the return value is a step-by-step walkthrough of screens, buttons and fields, and that no official MCP server exists so an OAuth2 client must be provisioned by an admin. This is meaningful behavioral context an agent cannot get from the annotations alone. It does not say how the target record/account context is determined.

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 core two-clause workflow is efficient, but the trailing API/OAuth2 paragraph is tangential to invoking this specific tool, and the '(checked 23 Oct 2026)' stamp adds noise. The most important fact — that this returns instructions rather than writing anything — is not the first thing stated.

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, annotation-covered, no-output-schema tool the description is mostly sufficient: it explains the return content and the required follow-up tools. However, it never explains how the note's target account/record is determined given there are no parameters, which is the one thing an agent would still wonder about before calling.

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 the schema carries no semantics to supplement and the baseline of 4 applies. The description correctly implies the call is parameterless by describing a fixed guidance response.

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 sentence 'Add note in the user's own SuiteCRM account' describes an action the tool does not actually perform; the real function (returning step-by-step instructions) only appears in the second sentence. An agent reading the name and first clause could reasonably expect a write operation, so the true purpose is stated but not front-loaded or unambiguous.

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 explicit workflow guidance: this tool returns the steps, and the actual execution happens via 'the cotlet_browser_* tools in the user's SuiteCRM Cloud Browser.' That is a clear use-then-follow-up sequence. It stops short of naming when NOT to use it or contrasting with the sibling record tools (suitecrm_create_task, suitecrm_log_call, etc.).

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