iva_conference_statistics

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. It does not state whether operations are read-only, whether exports create files or return data, whether any actions require confirmation, or what side effects occur. The schema reveals a 'confirm' parameter hinting at destructive actions, but the description never addresses this, leaving the agent without critical behavioral context.

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 relatively short and front-loads the tool's purpose. However, it is a single run-on-style list rather than structured guidance, and the final clause 'Clients API v2.28.12' does not earn its place for an agent selecting or invoking the tool. It is concise but not optimally structured.

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?

This is a complex dispatcher with 17 actions and 11 parameters, no annotations, and no output schema. The description does not explain how to select among the many actions, which parameters are required for each action, how date ranges and pagination work, or what the export operations return. The schema's action descriptions help, but the top-level description leaves too much unspecified for such a multifaceted tool.

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 100%, so the baseline is 3: all parameters already have descriptions, and the action enum has detailed bilingual explanations for each operation. The top-level description adds no parameter-level meaning beyond loosely naming categories like 'export to CSV' and 'sessions statistics aggregation.' This is acceptable because the schema does the heavy lifting.

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 identifies the tool's domain: conference statistics, including session/participant stats, activity, aggregation, and CSV export. It is recognizable as distinct from sibling tools like iva_conference_session or iva_conference_participants because it explicitly centers on statistics rather than session management or participant management. However, it does not name a single verb+resource, instead summarizing a multi-action dispatcher, and the trailing 'Clients API v2.28.12' adds noise.

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?

There is no guidance about when to use this tool versus the many sibling conference tools, nor any mention of alternatives or exclusions. The description implies a statistics-gathering role but does not state conditions like 'use for analytics/reporting' or 'use iva_conference_session for session management.' The detailed per-action guidance lives in the schema, not in the description.

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