studio_inspect_job

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

No annotations are provided, so the description carries the full burden; it does at least imply a read-only inspection and discloses that it performs consistency verification, which is meaningful behavioral context. However, it says nothing about whether verification has side effects, cost/rate characteristics, or error behavior for inconsistent chains. The output schema handles return-value explanation.

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 short sentence with no waste, but it is under-specified rather than efficient; the brevity buys no clarity and omits basic scoping information the agent needs.

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?

Because an output schema exists, return values needn't be described, and a one-parameter read tool is simple enough that this is nearly adequate. Still, with eight sibling tool and zero annotation coverage, the definition leaves key questions (what state, when to prefer it over studio_status or studio_reconcile_job) unanswered.

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?

There is one required parameter (job_id) at 0% schema description coverage, and the description adds nothing about it — no format, no source, no example. With coverage this low, the description should have compensated by explaining what a job_id refers to and how to obtain one, and it does not.

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?

It gives verbs (read, verify) and objects (durable state, event-chain/snapshot consistency), so the general intent is inferable from the name plus text. But it never says the resource is a job, and 'durable state' is abstract jargon that could mean many things. Nothing distinguishes it from close siblings like studio_status, studio_recovery_report, or studio_reconcile_job.

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 statement of when to call this versus the many other studio_* introspection tool, no prerequisites, and no exclusions. The agent must guess whether this is a pre-recovery check, a general status read, or a diagnostic.

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