job_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description adds nothing beyond that - it does not say whether the call blocks, whether results are cached, or what the returned state values are, giving no extra behavioral context.

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?

It is a single waste-free sentence, which is structurally sound, but the brevity stems from under-specification rather than disciplined concision, so it cannot score high on this dimension alone.

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?

There is no output schema, so the description would need to convey what a status response contains (e.g., queued/running/done/failed) and how to obtain a job_id, and it does none of this. For a status-polling endpoint these omissions leave the agent unable to interpret results correctly.

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 required parameter job_id, so the description carries the full burden of explaining it. It says nothing about where the job_id comes from (presumably execute/execute_file/render_view) or its format, leaving the parameter undocumented in both the schema and the text.

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 identifies the resource ('long-running CAM or rendering job') and implies a retrieval of its state, which is enough to guess the tool's role. However, it is a bare noun phrase with no explicit verb and no differentiation from siblings such as execute or render_view, which are the tools that presumably create these jobs.

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?

There is no guidance on when to call this tool, no mention of polling for long-running work, and no reference to alternatives or the tools that produce the job_id. The agent must infer the entire usage context from the name.

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