send_prepared_video

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

The tool clarifies a specific operational behavior—the absence of automatic resending post-request—which is a key piece of behavioral transparency not covered by the provided safety or hint annotations. This helps agents manage post-call expectations.

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?

The definition is extremely concise, using two sentences where the first sentence captures the primary action and the second provides the crucial behavioral constraint with zero fluff.

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 tool with only one required parameter, the definition is robust. It defines the action, the specific input required, and a major operational limitation, making it highly useful for correct tool invocation.

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?

Given the minimal input schema, the description adds crucial meaning by clarifying that 'job_id' refers to the 'preparation ID' (準備ID), helping the agent map the abstract parameter name to the necessary resource identifier.

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 is highly specific, stating it 'attaches the video' for a 'preparation ID.' This clearly distinguishes it from preparation steps or generic video upload tools within the posting workflow.

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?

It provides critical guidance on usage by specifying a behavioral constraint: 'Does not automatically resend after the post request.' This helps agents understand the tool's limitations relative to a hypothetical tool that might handle auto-resending.

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