start_shelf_refresh

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

With no annotations, the description carries the full burden and doesn't state whether this is an async job (implied by the existence of get_shelf_refresh_job), what state it mutates, or what happens if confirm is false. "Event-observed" hints at an observable job model, but only barely.

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 or repetition. It is efficient, though the terseness comes at the cost of the missing information scored elsewhere.

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?

This is an async, state-changing job starter with an output schema (so return values needn't be spelled out) but no annotations and 0% parameter documentation. The description should at least mention that it kicks off a job tracked via get_shelf_refresh_job and what the confirmation gate enforces; neither is present.

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%, so the description must compensate. It does partially: "one Painter shelf" maps to shelf_name and "after confirmation" maps to the confirm boolean. However it never explains the semantics of confirm (default false – does the call no-op without it?) or the required shelf naming expectations.

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?

"Start ... discovery for one Painter shelf" gives a verb and a resource, but the qualifier "event-observed discovery" is internal jargon that doesn't plainly say what happens (a rescan of a shelf's contents?). It also fails to distinguish the tool from siblings like get_shelf_refresh_job or import_shelf_resource.

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 only usage cue is "after confirmation," which gestures at a precondition but never explains when to call this versus get_shelf_refresh_job (the polling counterpart) or import_shelf_resource. No when-not conditions or alternatives are named.

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