get--v3-domain-tag-stats

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get stats by tag' implies a read-only operation but doesn't specify authentication requirements, rate limits, pagination behavior, error conditions, or what the output looks like (no output schema exists). For a tool with 10 parameters and no annotation coverage, this is a significant gap in behavioral transparency.

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. While this represents under-specification rather than ideal conciseness, it contains no wasted words and is front-loaded with the core purpose. Every word earns its place, though more content would be needed for a complete 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?

Given the complexity (10 parameters, 3 required), zero schema description coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what type of stats are retrieved, what the parameters mean, how to interpret results, or how this differs from similar tools. For a statistical retrieval tool with significant parameter complexity, this description provides insufficient 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 10 parameters have descriptions in the schema. The tool description 'Get stats by tag' only mentions one parameter ('tag') and doesn't explain the purpose of the other 9 parameters (domain, start, end, resolution, duration, provider, device, country, event) or their relationships. This fails to compensate for the complete lack of schema documentation.

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 'Get stats by tag' restates the tool name 'get--v3-domain-tag-stats' in a tautological manner. It specifies the verb 'Get' and resource 'stats by tag', but doesn't clarify what type of stats (e.g., email analytics, performance metrics) or what domain context is involved. It fails to distinguish this tool from sibling tools like 'get--v3-domain-tag-stats-aggregates' or 'get--v3-domain-stats-total'.

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--v3-domain-aggregates-countries', 'get--v3-domain-tag-stats-aggregates'), there's no indication of what makes this tool unique or when it should be selected over similar tools. No prerequisites, exclusions, or alternative recommendations are mentioned.

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