get_project_creation_job

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It never says whether this blocks, whether it is safe to poll repeatedly, what it returns while the job is still running, or what error surfaces for an unknown job — only that it reads 'terminal state' and 'file verification'.

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 of ten words with zero filler; the object of the read is placed before any qualification. Nothing in it could be trimmed without losing content.

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 values need not be explained, but the tool is still under-specified for its async-job role: no polling guidance, no null-job_id behavior, and no mention of the companion creation tools. For a job-inspection endpoint with a deliberately nullable key, the description leaves the operational essentials unstated.

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% and the single parameter job_id is optional with a null default, which is a semantically significant fact the description completely ignores. An agent cannot tell from the description what happens when job_id is omitted (most recent job? error? listing all?), so almost no meaning is added beyond the 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?

The description names a specific verb ('Read') and a specific resource ('terminal state and file verification for an asynchronous project creation'), which an agent can map to a job-status tool. It does not, however, name the sibling that starts such jobs (create_project/plan_project_creation), so differentiation relies on the reader's knowledge of the async pattern.

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?

Use is only implied: the phrase 'for an asynchronous project creation' suggests calling this after kicking off a creation job, and the sibling set (get_bake_job, get_mesh_reload_job, get_shelf_refresh_job) reinforces that pattern. There is no explicit when-to-use, no alternative named, and no statement about polling or when to stop.

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