Fflgetsessionevents

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

No annotations are provided, so the description carries the full behavioral burden. It reveals only that this is a read of 'recent' events; it says nothing about behavior when the session is stopped, how far back 'recent' reaches, ordering, or any auth/limit behavior — significant gaps for an unannotated tool.

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?

A single, front-loaded sentence with zero waste. However, the brevity is partly under-specification rather than true economy given the undefined jargon and undocumented parameters.

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?

An output schema exists, so return values needn't be explained, but with no annotations, 0% parameter coverage, and undefined 'hook events', an agent still lacks enough context to call this confidently or know when to prefer it over siblings.

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 0%, so the description must explain sessionId and limit, but it says nothing about either. 'Recent' only vaguely gestures at the limit parameter, and the schema gives no description of the default of 50 or expected sessionId format.

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?

Specific verb+resource: 'Get recent hook events for a running session' tells the agent it retrieves event data rather than session metadata, distinguishing it from siblings like fflGetSession and fflListSessions. The term 'hook events' is domain jargon left undefined, which slightly limits precision.

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 on when to call this versus fflGetSession or fflListSessions, and no mention of what to do when a session isn't running. The phrase 'for a running session' hints at a prerequisite but never states it as a condition or exclusion.

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