chatwoot_list_labels

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds useful scope context ('all labels in the account') and return fields, but does not disclose behaviors like pagination, limits, or authentication requirements.

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 with the core purpose. The label-purpose sentence is a small useful addition, though the 'Args: output_format: Output format.' line duplicates the schema without earning its place.

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 list tool with one optional enum parameter, an output schema, and safety annotations, the description is reasonably complete: it gives the resource scope and output fields. It could be improved by naming the sibling tool for label performance metrics, but nothing critical is missing for a correct call.

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 output_format, but the description merely repeats 'Output format' without adding meaning beyond the schema's enum. With 0% schema description coverage, the description was expected to compensate but instead stays tautological.

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 verb and resource: 'Lists all labels in the account' and even names the result fields (ID, color, description). This clearly distinguishes it from sibling tools like chatwoot_list_agents or chatwoot_get_label_performance.

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 line 'Labels are used to tag and categorize conversations' gives some contextual value, implying use for understanding label purposes. However, it does not explicitly say when to choose this tool over alternatives, nor provide any exclusions or when-not-to-use guidance.

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