Get ScreenApp recording

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the 'legacy' qualifier, which is useful context (implies there may be non-legacy recordings). It doesn't contradict annotations and adds a small but relevant detail beyond the structured fields.

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, zero filler. The first sentence states purpose and scope; the second routes to alternatives. All information is front-loaded and 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 simple read-only metadata retrieval with one well-documented parameter and safety covered by annotations, the description is complete. It specifies the resource type ('legacy'), gives alternatives for other data, and no output schema exists so return format explanation is not required. Nothing an agent needs to call it correctly 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?

Schema coverage is 100% for the single parameter fileId, with a clear description ('ScreenApp recording/file UUID'). The description does not add parameter-specific detail, but none is needed since the schema fully documents it. Baseline 3 applies.

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 action ('Get metadata') and the resource ('one legacy ScreenApp recording'). It also explicitly differentiates from siblings by directing transcript text to get_transcript and stored summary to get_summary, so the agent knows exactly what this tool does not return.

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 explicit when-to-use guidance: it tells the agent to use get_transcript for transcript text and get_summary for its stored summary. This makes it clear that this tool is for metadata only, and names the alternatives precisely.

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