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

Beyond the readOnlyHint and idempotentHint annotations, the description importantly discloses that the tool 'opens nothing by itself' and returns procedural guidance with screens, buttons, and fields. This prevents the agent from mistaking it for a direct browser action, though it could be clearer about the exact return format.

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 workflow is stated clearly and early, but the opening phrase 'from ChatGPT, Claude or any AI agent' is marketing filler, and the trailing 'Chargebee's official API: Yes.' is cryptic and does not earn its place. The description could be tightened without losing meaning.

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, the description adequately explains what it returns and how to proceed with browser tools. It does not provide a detailed output schema, but none exists, and the description covers the essential workflow.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter meaning, and the schema coverage is 100%.

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 (customer in Chargebee) and clarifies that the tool returns step-by-step instructions rather than performing the action itself. It distinguishes its role from the cotlet_browser_* tools by stating that those tools are used afterward, though the name 'find_customer' could momentarily suggest direct execution.

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 implies the workflow: use this tool to get instructions, then use cotlet_browser_* tools to perform the action in the user's Chargebee Cloud Browser. However, it does not explicitly state when to choose this over sibling tools like cotlet_app_guide or when not to use it, leaving some inference to the agent.

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