chatwoot_list_teams

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the safety profile is clear and not contradicted. The description adds the account-level scope but does not disclose other behavioral traits such as pagination, ordering, limits, or how the output_format parameter changes the result.

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 description is short and front-loaded, but the 'Args: output_format: Output format.' line is redundant with the input schema. It is concise but not efficiently informative, and the space could have been used to clarify output format behavior or usage context.

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 simple read-only list tool with one optional schema-defined parameter and an output schema, the core operation is adequately covered. However, missing usage guidance and the lack of meaningful parameter semantics leave notable gaps for an agent deciding whether and how to invoke it.

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 only parameter is described as 'Output format,' which adds no meaning beyond the schema's enum and default values. Schema description coverage is 0%, and the description fails to compensate by explaining what each output format yields or why an agent would choose one over the other.

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 clear operation: 'Lists all teams in the account,' identifying both the resource (teams) and the account scope. It does not explicitly distinguish itself from sibling tools like chatwoot_get_team_performance, but the verb 'lists all' makes its purpose unambiguous.

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?

There is no guidance about when to use this tool versus alternatives, no mention of related read-only tools, and no exclusionary context. The description simply states what it does without helping an agent decide when it is the right choice.

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