get_chat_analytics

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It describes what the tool returns and the channel scope, but does not mention side effects, authentication, rate limits, or read-only assurances. The 'Get' verb implies a safe read, but this is not explicit.

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 two sentences, front-loaded with the purpose, and contains only essential information. No redundancy or filler.

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?

Despite having an output schema (not shown), the description lists the key KPIs, which is useful. However, with 5 undocumented parameters and no annotations, the overall context is incomplete. The description gives basic usage but lacks deeper parameter guidance and edge-case behavior.

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?

Schema description coverage is 0% for all 5 parameters. The description adds some context ('SMS + WhatsApp' hints at valid channel values, 'requested window' relates to start/end dates) but does not explain the interval parameter, agent_id, or how parameters interact. With no schema descriptions, the description insufficiently compensates for the low coverage.

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 clearly states the tool retrieves chat-channel KPIs (SMS + WhatsApp) and enumerates specific metrics (inbound/outbound counts, latency, agent utilisation, outcomes). This is a specific verb+resource and distinguishes it from the sibling tool get_combined_analytics.

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?

Explicitly names an alternative tool: 'For combined voice + chat KPIs use get_combined_analytics instead.' This provides clear when-to-use/when-not-to-use guidance and differentiates the tool from a closely related sibling.

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