refresh_owned_exam_adapter

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

With no annotations, the description does carry useful behavior: it is a targeted reload that preserves browser, capture and review state, which tells the agent it is non-destructive to surrounding session state. It omits what happens on a non-idle adapter, whether the reload is synchronous, and what the result looks like.

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?

One clause pair, front-loaded with the action and scope, then the state-preservation guarantee. Every word 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 parameterless, no-output-schema tool, an agent still needs to know the idle precondition's failure mode and whether a result/status is returned; neither is covered. Adequate but leaves a real gap for an operation with no annotations to lean on.

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?

Zero parameters, so there is nothing to document and the baseline is 4. The description correctly adds no parameter noise.

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?

States a specific verb+resource: reloading the exam adapter, narrowed to the idle instance. That distinguishes it from the many refresh_* siblings (refresh_exam_browser, refresh_direct_implementation) at a high level, though 'adapter' is internal jargon an agent must infer.

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?

'only the idle exam adapter' implies a precondition (adapter must be idle) but never says when to pick this over refresh_exam_browser or refresh_inventory_implementation, nor what to do if the adapter is not idle. Usage is implied rather than prescribed.

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