yaaif_ops_session_insights

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

The description declares READ-ONLY, which is a useful behavioral cue. However, with no annotations provided, the description must carry the full burden of behavioral disclosure. It reveals nothing about side effects, performance characteristics, output size, or pagination behavior, leaving agents to guess.

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 short, but this is under-specification, not conciseness. It omits essential information, so the brevity is not a virtue. A well-structured concise description would still convey purpose, usage, and key behaviors.

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?

The tool has 5 parameters, no output schema, and no annotations. The description must explain what insights are, how to interpret results, and what the parameters control, but it does none of that. It is completely inadequate for an agent to call this tool correctly.

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 description adds zero information about parameters. Schema coverage is 60% (3 of 5 parameters have descriptions), but session_id and include_raw lack descriptions, and the description doesn't compensate. It offers no hints about parameter meaning, defaults, or interactions.

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 states 'flow-session insights' but lacks a specific verb or resource. It is an alias of yaaif_ops_telemetry resource=insights, but this cryptic reference doesn't clarify what the tool actually returns or does. It doesn't distinguish from siblings like yaaif_ops_session_get or yaaif_ops_session_events.

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 on when to use this tool versus alternatives. The alias reference is ambiguous and doesn't explain when to prefer this over yaaif_ops_session_get, yaaif_ops_telemetry, or other ops tools. No conditions or exclusions are given.

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