get--v3-stats-total

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states 'Totals for entire account,' which doesn't indicate whether this is a read-only operation, what data it returns, any rate limits, authentication requirements, or potential side effects. For a tool with 5 parameters and no output schema, this lack of behavioral context is severely inadequate.

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 extremely concise at just three words, which is front-loaded and wastes no space. However, this brevity comes at the cost of under-specification—it's too terse to be helpful. While structurally simple, it lacks the necessary detail for effective tool use.

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?

Given the complexity (5 parameters, 1 required, no schema descriptions, no annotations, no output schema), the description is completely inadequate. It doesn't explain what the tool does beyond a vague notion of 'totals,' leaving the agent guessing about behavior, parameters, and output. For a stats-related tool with multiple inputs, this fails to provide any meaningful context.

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 schema description coverage is 0%, meaning none of the 5 parameters (start, end, resolution, duration, event) are documented in the schema. The description 'Totals for entire account' adds no meaning about these parameters—it doesn't explain what 'event' refers to (the only required parameter), how date ranges work, or what 'resolution' and 'duration' control. This fails to compensate for the schema gap.

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 'Totals for entire account' restates the tool name 'get--v3-stats-total' in a tautological way. It doesn't specify what kind of totals (e.g., statistics, metrics, counts) or for what resource (e.g., emails, events, domains). While it implies account-level scope, it lacks a clear verb and specific resource, making it vague compared to siblings like 'get--v3-domain-stats-total' which clearly targets domain statistics.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context, or sibling tools like 'get--v3-stats-filter' or 'get--v3-domain-stats-total' that might be relevant for filtering or domain-specific stats. Without such information, an agent cannot determine appropriate usage scenarios.

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