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

The annotations already declare readOnlyHint=true, and the description adds that the response covers status, cost, and output, which is genuinely useful behavioral context. However, it does not disclose what happens for pending/failed jobs, whether cost is final or estimated, or any error behavior beyond the read-only safety profile.

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 no filler; the verb, scope, and return facets all appear immediately and nothing is wasted.

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 the return value doesn't need explaining, and the read-only hint covers safety for this simple one-parameter tool. What's missing is provenance for job_id and any note on job-state semantics, which matter even for a trivial lookup.

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 integer parameter, so the schema contributes no meaning. The description only implies job_id identifies 'one 3D job' but doesn't say where the ID comes from (create_3d), its format, or how invalid/missing IDs behave — leaving a real gap on the only parameter.

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 states a specific verb+resource ('Get ... one 3D job') and enumerates the returned facets (status, cost, output), which implicitly differentiates it from list_3d by scope (single vs. list). It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

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?

Usage is only implied by 'one 3D job' — the agent can infer this is the single-job lookup as opposed to list_3d, but the description never says when to call it (e.g., polling a job created by create_3d) or what to do instead when the job_id is unknown.

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