chatwoot_list_captain_assistants

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds account-scoped context and 'all' helpers. It does not disclose additional behavioral details such as ordering, pagination, or permissions, but for a simple read-only list this is acceptable.

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 first sentence is clear and front-loaded with the action and resource. The 'Args' section is redundant with the schema and adds slight noise, but the overall definition remains compact.

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?

The tool is a simple read-only list operation with one optional parameter, and the schema's enum/default plus annotations cover most invocation needs. The only remaining gap is the lack of meaningful paramter description, which is already reflected in the parameter_semantics score.

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 description's paramter entry 'output_format: Output format.' only restates the parameter name and adds no new meaning. With schema description coverage at 0%, the description fails to compensate; the enum and default in the input schema are the only real guidance for valid values.

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 states a specific action ('Lists'), a specific resource ('Captain (AI) assistants'), and scope ('configured in the account'). This clearly distinguishes it from sibling tools like chatwoot_list_agents or chatwoot_list_inboxes.

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 implies the tool should be used when an agent needs to enumerate Captain assistants, but it does not explicitly discuss when to prefer it over related listing tools or mention exclusions. Usage intent is inferred from the resource name rather than stated.

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