Get actor B-roll default

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

Consistent with readOnlyHint=true and destructiveHint=false, and it adds genuinely useful context beyond annotations: the setting is stored-only and never affects actor-only videos, and run-level overrides take precedence over the account actor default. It does not cover auth/scope requirements or what happens when no default is saved.

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?

Front-loaded with the purpose and generally economical, but the policy enumeration ('anyone/no_actor/no_people including hands') and the isolated 'Segmented media generation is closed.' sentence are dense and partly unclear rather than efficiently informative.

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 read tool with no output schema, the description covers value semantics and fallback precedence ('override wins; otherwise no_people'), which is close to complete. It still leaves open the behavior when the actor has no saved default.

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 0% and the description never mentions actor_id, so the single required parameter is documented only by its self-explanatory name. With just one obvious identifier this gap is minor, but the description adds no meaning 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?

States a specific verb and resource: 'Read this account actor's saved B-roll default.' That is clearly distinct from the sibling set_actor_defaults, though the description never names that sibling to make the read/write split explicit.

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?

Explains how to interpret the stored value but gives no guidance on when to call this versus set_actor_defaults or get_run/get_run_shots, and states no preconditions or exclusions.

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