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

With no annotations provided, the description bears full burden for behavioral disclosure. It states it returns 'recording metadata including name, platform, device, step count, and timestamps' which gives some output expectations. However, it doesn't disclose auth requirements beyond 'authenticated user', default result limits, ordering behavior, or error semantics. Reasonable but incomplete.

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?

Single concise sentence that front-loads the primary action and follows with useful return-value context. No wasted words or redundant restatement of the tool name. Efficient and readable.

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?

For a list tool with a rich input schema (5 well-documented optional filters) and no output schema, the description is adequate but not complete. It covers the core purpose and return metadata but omits details like default pagination behavior, whether results are ordered, and how to combine filters. Given no annotations, the description could reasonably disclose rate/size limits or result truncation behavior.

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 schema fully documents all 5 parameters. The description adds the return-metadata context (name, platform, device, step count, timestamps) which helps an agent understand what fields might be present. Baseline 3 is correct since schema handles parameter documentation, though the description could note defaults or combination semantics for limit/offset.

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 the tool lists flow recordings belonging to the authenticated user, with a specific verb ('List') and resource ('flow recordings'). It distinguishes from siblings by clarifying scope (authenticated user's recordings), which differentiates from flow_recording_get (single) and flow_recording_start (create). However, it doesn't explicitly contrast against the many related flow_recording_* tools.

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 vs alternatives like flow_recording_get, flow_recording_replay, or device_record_list. It mentions filtering parameters implicitly through the 'including... metadata' phrase but offers no exclusions or alternative tool references. Context for pagination or default behavior is absent from the description body.

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