chatwoot_get_conversation_traffic

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

The annotations already declare the tool read-only and non-destructive, and the description does not contradict this. It adds the behavioral context that the result is a heatmap, but does not disclose timezone semantics, data granularity, or other operational details. Given the simple read-only nature, annotations carry most of the burden.

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 compact and front-loaded with the core purpose. The 'Useful for' sentence adds genuine usage context. The Args block is redundant with the schema but is minimal enough not to significantly bloat the description.

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 analytics tool with two optional enum parameters, defaults, an output schema, and read-only annotations, the description covers the core purpose and use-case. It is incomplete mainly in parameter semantics and explicit differentiation from sibling tools, but it remains adequately usable for selection and invocation.

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 Args block merely restates the schema titles: 'period: Analysis period' and 'output_format: Output format'. With schema description coverage at 0%, the description was expected to compensate by explaining enum values, units, or format differences, but it adds no meaning beyond what the schema already provides.

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 opens with a specific verb and resource: 'Returns a conversation traffic heat map (hour × day of week)', which clearly identifies the tool's function. This output type is unique among the sibling analytics and conversation tools, so the purpose is 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?

The sentence 'Useful for identifying peak hours and staffing teams appropriately' gives a clear context for when this tool is relevant. However, it does not mention alternatives or explicitly state when not to use it, stopping short of full routing guidance.

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