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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: it names the access restriction (owned by the authenticated Site owner) and the three key pieces of data returned, including a 'private draft' and an 'independent gate result'.

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 that starts with the verb and contains no filler. Every element ('status, private draft, independent gate result', ownership scope) earns its place.

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?

For a low-complexity, single-parameter read tool with no output schema and rich read-only annotations, the description is nearly sufficient. It names the returned fields, though it omits any detail about output format, error cases, or pagination behavior.

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 jobId parameter. The description implies that a job identifier is needed and that it must refer to a job owned by the caller, but it does not explain the UUID format, where the ID comes from, or any other syntax beyond what the bare schema already supplies.

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 ('Read'), resource ('Owner Studio writer job'), and the exact information returned (status, private draft, gate result), and scopes it to jobs owned by the authenticated Site owner, distinguishing it from the sibling publish/submit tools.

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?

No explicit when-to-use, when-not-to-use, or alternative tool is mentioned. The purpose implies inspection of an existing job, but the description gives no conditions or prerequisites for invoking it versus the sibling newsroom tools.

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