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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the call 'opens nothing by itself' and returns procedural text rather than invoice records. It does not describe response shape in detail, and the trailing 'Chargebee's official API: Yes.' is too vague to count as disclosure.

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 behavior is front-loaded and stated compactly, which is good. However, the closing fragment 'Chargebee's official API: Yes.' is a dangling, ambiguous claim that adds no actionable meaning and reads like leftover metadata. Removing it would strengthen the definition without information loss.

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 ('step by step (screens, buttons, fields)'). It also tells the agent what to do next via the browser tools, closing the loop. The unexplained 'official API' remark is the only loose end.

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 for the description to clarify and the baseline of 4 applies. No parameter misinformation is present.

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 (overdue invoices) and explicitly corrects the expectation set by the name: it 'Returns how to do it in Chargebee step by step (screens, buttons, fields) and opens nothing by itself.' That tells an agent this is a guidance tool, not a data-fetching tool, which distinguishes it from the chargebee_mutation siblings. The remaining friction is that the tool name/title promise a listing while the body promises instructions, requiring the agent to read past the name.

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 an explicit sequencing rule: call this for the steps, 'then do it with the cotlet_browser_* tools in the user's Chargebee Cloud Browser.' That is actionable routing to the correct sibling family. It stops short of stating when NOT to use it (e.g., when the agent already knows the Chargebee UI flow), so it falls short of a 5.

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