agnes_video_query

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

Discloses key behavior: async status query, completion condition, and result field (remixed_from_video_id). No annotations provided, so description carries full burden. Could add detail on polling behavior or error states, but adequate.

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 with no waste. Front-loads purpose, then usage, then result. Every sentence 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?

Given no output schema and 3 optional params, description explains query methods and result. Lacks mention of error handling, timeouts, or auth. But for a simple query tool, it's fairly complete.

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%, baseline 3. Description adds meaning beyond schema: video_id is recommended, task_id is legacy, model_name overrides default. Clearly explains the two query methods.

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?

Clearly states the tool queries the status/result of an async video task, specifying the two query methods (video_id recommended, task_id legacy) and what happens on completion. Distinct from siblings like agnes_video_create and agnes_video_wait.

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?

Provides clear guidance on which parameter to use (video_id recommended, task_id legacy). Implicitly tells when not to use this tool (e.g., when needing to create or wait for video). No explicit when-not-to-use, but sufficient.

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