display_record

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

The annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description does not contradict them. It adds a useful behavioral detail—the response is an MP4 returned as base64—but otherwise reveals no constraints like maximum duration, resolution, or whether audio is captured.

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?

One sentence with no filler; the essential action and return type are front-loaded. Every word earns its place.

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 one-parameter tool the core is present—what to do and what will come back—but missing parameter semantics and the vague 'short' upper bound leave gaps. There is no output schema to fill in return details, though the description does state MP4/base64.

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% and the description never names or explains duration_seconds. The 'short' qualifier implies small values and the parameter name self-documents seconds, but there are no bounds, constraints, or additional semantics added by the description.

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?

Names the action ('Record'), the resource ('screen clip'), and the exact return format ('MP4 as base64'). The verb is specific enough to distinguish from static-capture siblings like display_screenshot or get_snapshot.

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 gives no explicit when-to-use guidance or alternatives. It is possible to infer that this is for short video rather than still images, but no condition, exclusion, or alternative is stated, so agents must decide without support.

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