design_job_result

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

No annotations exist, so the description carries the full burden. It does disclose the key non-obvious trait — that the return is None while the job is unfinished — but says nothing about whether the payload is consumed/cleared on read, what happens with an unknown job_id, or whether the call is idempotent.

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?

A single front-loaded sentence with zero filler; the most important constraint (None until done) is included rather than padding.

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?

An output schema exists, so return formatting need not be explained. Still missing is the surrounding workflow: no pointer to design_job_status for polling, no statement on error behavior for invalid or expired job_ids, in a family of three job tools where the ordering matters.

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 description coverage is 0% for the single job_id parameter, and the description never says where a job_id comes from (presumably design_job_start) or what format it takes. The parameter name is fairly self-explanatory, which keeps this from a 1, but the description adds no meaning beyond the name.

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 ("Fetch a finished job's result payload"), which cleanly separates it from a status tool. It does not name its siblings (design_job_start / design_job_status), so an agent must infer the workflow from the description alone.

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?

The parenthetical "None until it's done" implies the caller should wait for completion before using this tool, which is real usage guidance. However, it never explicitly points to design_job_status as the way to check completion, nor states what to do while the job is running.

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