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

Annotations already mark readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about the response contents, including domains, brand colour, links, embed token, and remaining quota.

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?

Single sentence with the core action and scope front-loaded, followed by a compact dash-separated list of return fields. No filler or redundancy.

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, read-only list tool, the description covers the input requirement, the expected returned fields, and the quota signal. Without an output schema, the enumerated fields substitute for return documentation, and annotations cover side effects.

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?

No parameters exist (schema coverage is 100% on an empty object), so there is no parameter meaning to supply. Baseline 4 applies; the description focuses on return contents rather than 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?

States a specific verb ('List') with a clear resource ('website chatbots on this account') and enumerates the returned fields. This distinguishes it from sibling tools like delete_chatbot or list_chatbot_documents.

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?

Description establishes the context of use: retrieving an inventory of the account's chatbots and remaining quota. It doesn't explicitly name alternatives or exclusions, but for a zero-parameter list tool the use case is clear enough.

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