Get Video Status

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

Beyond the readOnly/idempotent annotations, it discloses pipeline semantics (which states are non-terminal and therefore require re-polling), the ID-type constraint, and an honest UNVERIFIED caveat about Reel IDs on this edge. That is exactly the kind of runtime behavior an agent cannot get from annotations.

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, then the polling rationale and ID caveat in three tight sentences. Slight redundancy with the schema on the video-vs-post ID rule, but 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?

For a two-parameter read tool with full schema coverage and an output schema, the description supplies everything else an agent needs: state vocabulary, polling cadence, the writer sibling that yields the ID, and an explicit uncertainty flag. Nothing material is missing.

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%, so both parameters are already documented, including the video-vs-post ID distinction and the default Page fallback for `profile`. The description restates the video_id semantics but adds no format detail or guidance on `profile`, so it neither compensates nor detracts — baseline 3 applies.

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 ('Poll where one video stands') and enumerates the exact states returned (uploading, processing, ready, error). It explicitly distinguishes itself from the writer sibling facebook_create_video_post, which returns the videoId prematurely.

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?

Gives explicit when-to-use guidance ('read the state here instead of assuming a fresh video is live') plus a concrete loop instruction: for non-terminal states, wait a few seconds and call again. It also names the alternative tool that produces the input, leaving nothing to inference.

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