seameet_get_recording

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

Adds behavioral context about content capping for free-plan owners, which is beyond the input schema. However, no annotations provided, so description could disclose more (e.g., read-only nature, auth requirements).

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 concise sentences: first covers main purpose, second lists artifacts and cap note. No filler.

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?

Describes main output and artifacts but does not detail 'metadata' contents. Missing prerequisite mention that assetId comes from list recordings. No output schema, so return format is vague. Lacks explanation for default section 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 coverage is 100% but description adds default value for 'section' parameter (summary) and lists enum options, providing clarity beyond the schema which lacks default specification.

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?

Description clearly states the verb 'Get', resource 'one recording', and what is returned: 'metadata plus a chosen artifact'. It distinguishes from sibling 'seameet_list_recent_recordings' by specifying 'one recording' vs listing.

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 explicit when-to-use or alternatives mentioned. The purpose and schema imply use after obtaining assetId from list recordings, but not directly stated.

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