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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it performs no action, opens no page, and returns a procedural walkthrough of screens, buttons and fields. It does not describe the exact shape of that returned walkthrough, which keeps it below a 5.

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 value — it returns instructions and does nothing itself — is front-loaded in the first sentence, with the hand-off to browser tools and the API caveat following. Wording is slightly tangled in 'Returns how to do it in ManyChat step by step', and the parenthetical '(checked 5 Nov 2026)' is a dated aside that adds little for an agent.

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-mutating tool with annotations already covering safety and no output schema, the description supplies everything needed: what it returns, that it takes no real-world action, which companion tools execute the follow-up, and the API constraint. Nothing essential to calling it correctly is missing.

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 there is nothing the description could additionally clarify at the argument level; baseline for a parameterless schema is 4. The description correctly spends no words on inputs.

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 verb and resource (send an inbox message in the user's own ManyChat account) and then immediately corrects an expectation the name creates: it returns step-by-step instructions (screens, buttons, fields) rather than performing the send. That correction is what makes the tool distinguishable from the name alone. It stops short of differentiating it from its manychat_* siblings such as manychat_send_broadcast.

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?

Clear sequencing guidance: this tool opens nothing by itself and the actual action follows via cotlet_browser_* tools in the Cloud Browser. It also gives a prerequisite-style fact (official API only on Pro plan or higher and narrow), which explains why the browser route is needed. No explicit statement about when not to use it or how it differs from the sibling broadcast/message tools.

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