List local recordings

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds genuinely new behavior: results are newest-first and each entry carries size and an optional videoId meaning 'already uploaded', which tells the agent how to interpret missing values. Minor gaps remain (empty state, whether any cap on count exists), so not a 5.

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?

Two sentences, front-loaded with the scope and ordering constraint, then the alternative route. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, and the description compensates by enumerating the returned fields and the semantics of the optional videoId. Combined with the annotation-covered safety profile and the explicit sibling routing, nothing needed to call or interpret this tool is missing.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning to supply. The description correctly spends its space on scope and return fields rather than inventing arguments.

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?

States a specific verb and resource ('List the recordings saved on this computer') plus the ordering ('newest first') and the shape of each item (takeId, size, timestamp, videoId). It explicitly contrasts itself with list_videos for cloud recordings, so an agent can separate it from the sibling without opening a schema.

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?

Provides an explicit when-not and a named alternative: recordings made while signed in to Recordful Pro go to the cloud instead, and the agent is routed to list_videos. That is the exact routing decision an agent needs for a local-vs-cloud listing choice.

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