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

The readOnlyHint annotation already signals this is a non-mutating operation. The description adds that the tool returns the full set of bundles, which is a meaningful behavioral guarantee beyond the annotation, and it lists the data fields returned.

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?

A single, information-dense sentence that front-loads the action and scope while also summarizing the output fields. Every part of the description earns its place, and there is no unnecessary repetition of the tool name or schema.

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 no-parameter, read-only list operation with an output schema, the description is fully sufficient. An agent can determine when to call it)Skip and what it will receive without needing additional context.

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 no parametershol, so the schema is already 100% descriptive. No additional parameter explanation is needed; the description correctly focuses on what the response contains.

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 uses a precise verb ('Lists') and identifies the exact resource ('every available CometChat implementation bundle') plus the returned fields. This makes it easy to distinguish from the singular get_cometchat_implementation_bundle and the search-focused search_cometchat_docs tool.

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?

The description clearly implies this is the enumeration/discovery tool for bundles, useful before fetching a specific bundle via get_cometchat_implementation_bundle. It does not explicitly state exclusions or name alternatives, but the zero-argument interface leaves little ambiguity in when it should be used.

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