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

The description usefully enumerates the three terminal states (generating / completed with the model / failed) and discloses that the preview polls it automatically, which is real context beyond the schema. However, the annotations declare readOnlyHint=false and idempotentHint=false for what reads as a pure status poll, and the description does not reconcile that or state polling/rate expectations, so the behavioral picture stays incomplete.

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?

Three short sentences, front-loaded with purpose and state outcomes before the auto-invocation note. No filler, no restatement of the title.

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?

With an output schema present, the description need not spell out return payloads, and it covers purpose, outcomes, and invocation triggers adequately. The remaining gap is the required-vs-optional identifier choice, which neither the description nor the schema explains.

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 100% and both params (jobId, artifactId) are already documented as coming from create_3d_model, which the description merely echoes. It adds nothing about why artifactId is required while jobId is optional or when each identifier should be supplied, so baseline 3 applies.

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 gives a specific verb+resource ("Check the status of a 3D model") and anchors it to the sibling that creates it (create_3d_model), which cleanly separates it from create_3d_model and from the analogous video_status sibling.

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?

It states clear usage context: the inline preview calls it automatically, and the agent should call it when the user asks whether their model is ready. It does not name a when-not condition or an alternative status tool (e.g. video_status for videos), so it stops short of the top score.

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