get_clip_metadata

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

No annotations provided, so description carries full burden. Describes basic behavior (get metadata by name from current folder) but does not disclose edge cases like clip not found, multiple clips with same name, or return format.

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 plus a parameter docstring. No wasted words, but the structure could be improved by front-loading the key purpose.

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?

Has output schema, so return values are covered. Describes the single parameter and context (current Media Pool folder). Lacks mention of existence requirement or uniqueness constraint, but adequate for a simple retrieval tool.

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?

Only parameter 'clip_name' is described with a terse restatement of the parameter name. Schema coverage is 0%, so description adds minimal value beyond the schema.

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?

Clear verb 'get' and resource 'all metadata for a clip' with specific context 'by name in the current Media Pool folder'. Distinguishes well from siblings like set_clip_metadata and get_clip_markers.

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?

Implies use when needing metadata for a specific clip by name, but no explicit when-to-use or when-not-to-use guidance. No mention of alternatives like set_clip_metadata_batch.

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