get_shelf_refresh_job

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

No annotations are provided, so the description carries the full disclosure burden. 'Read persistent state' implies a safe, non-mutating operation and that state survives beyond the call, but nothing is said about behavior with an unknown job_id, job expiry/retention, or concurrency concerns.

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 efficient sentence with the resource front-loaded and zero filler. It is terse to the point where a little more content (polling/lifecycle) would have earned space, but nothing present 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 return-value explanation is not needed, and a one-optional-parameter getter is simple. Still, the relationship to start_shelf_refresh and the meaning of a job's lifecycle are unstated, leaving the agent to infer the workflow.

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 coverage is 0% for the single optional job_id parameter, so the description must compensate. 'Latest or selected' does add real meaning — omitting job_id returns the newest job — but it does not clarify format, validity, or error behavior for an unknown id.

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 uses a specific verb ('Read') on a specific resource ('persistent state ... shelf refresh job'), which cleanly separates it from the sibling 'start_shelf_refresh' that initiates a job. It stops short of naming that sibling explicitly, but the read-versus-start distinction is inferable from the text alone.

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?

The phrase 'latest or selected' implicitly tells the agent it can call this without a job_id to get the newest job, but there is no explicit when-to-use guidance, no mention of calling it after start_shelf_refresh to poll progress, and no named alternative.

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