cigchat_flow_custom_events_data

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

With no annotations, the description carries the disclosure burden. It does disclose the required 'Manage Flow' scope and implies a safe read operation via 'GET'. However, it does not mention pagination, response format, or other behavioral details, though the read-only intent is fairly 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 short sentences containing the action, resource, endpoint, and auth requirement. There is no redundant phrasing or filler, making it concise and front-loaded.

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 5 parameters and no output schema, the description only states the purpose and auth scope. It does not clarify what the returned 'data' contains or how this tool differs from the closely named flow_custom_events_summary, leaving the agent under-informed for selection and invocation.

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 input schema already provides descriptions for all 5 parameters, giving 100% schema coverage, so the baseline is 3. The description adds no parameter-specific meaning, which is acceptable because the schema fully documents each field and the time-window constraint.

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 a GET operation for 'flow custom event data' and includes the exact endpoint. The word 'data' distinguishes it from sibling tools like flow_custom_events_summary, making the resource and action unambiguous.

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?

No guidance is provided on when to use this tool versus similar siblings such as flow_custom_events_summary or list_custom_events. The only contextual note is the auth scope requirement, which is not enough to direct tool selection.

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