check_job_status

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

Discloses that it's safe to call repeatedly, does not consume job state. Details response fields for each status (completed, failed, processing). No annotations provided, so description carries full burden and does it well.

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?

Paragraph is well-structured and front-loaded with purpose. Each sentence adds value. Could be slightly more concise but is efficient overall.

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 the tool's simplicity (one param, no output schema), the description covers purpose, usage, behavior, and response fields completely. No gaps.

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 jobId has schema description 'The job ID returned from a create_* call when immediatePollUrl=true or when callback_url was omitted.' Schema coverage 100%, but description adds context about where jobId comes from, adding value beyond 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?

Description clearly states 'Poll for the result of an async presentation job' and specifies it's used after any create_* call that returned a jobId. This distinguishes it from sibling create tools.

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?

Explicitly says 'Use after any create_* call that returned a jobId' and provides recommended polling cadence (55-60s first, then 30-35s). No explicit when-not, but context is clear.

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