post--v2-bounce-classification-metrics

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'List statistic v2' gives no information about whether this is a read-only operation, whether it requires authentication, what rate limits apply, what the response format looks like, or whether it's paginated. For a POST endpoint with 9 parameters and no output schema, this is critically insufficient.

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?

While technically concise (three words), this is under-specification rather than effective brevity. The description fails to communicate essential information and wastes its limited space. A proper description would be longer but more helpful - this is too short to be useful.

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 (9 parameters, nested objects, no output schema, 44% schema coverage, no annotations), the description is completely inadequate. It doesn't explain what bounce classification metrics are, what time ranges apply, how dimensions/metrics work, what the POST method implies, or what results to expect. The agent cannot use this tool effectively with such minimal information.

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 only 44%, meaning most parameters lack documentation in the schema. The description 'List statistic v2' adds zero information about what the 9 parameters mean, how they interact, or what values are expected. It doesn't compensate for the poor schema coverage, leaving the agent guessing about parameter usage.

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 'List statistic v2' is a tautology that essentially restates the tool name 'post--v2-bounce-classification-metrics'. It doesn't specify what resource is being listed (bounce classification metrics), what 'v2' refers to, or how this differs from sibling tools like 'get--v1-bounce-classification-stats'. The purpose is vague and lacks differentiation.

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. With many sibling tools available (e.g., 'get--v1-bounce-classification-stats', 'post--v1-analytics-metrics', various domain-specific tools), there's no indication of context, prerequisites, or exclusions. The agent receives no help in selecting this tool appropriately.

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