bitpull_recheck_setup

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

The only annotation is destructiveHint=false, so the description carries nearly the full burden. It does not say whether this is a passive probe or whether it mutates stored setup state, whether it can be slow (Docker/Ollama probing often is), or what it returns to the caller.

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 filler and the subject matter front-loaded. It is terse rather than padded, so it earns its length, though the brevity comes at the cost of the missing detail noted 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?

For a zero-parameter probe with no output schema, an agent still needs to know what the recheck produces and whether it changes setup state. None of that is covered, so the definition is materially incomplete for its complexity.

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?

The tool takes zero parameters, so the schema has nothing to explain and there is no parameter semantics gap to fill. The description is not required to add anything here.

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 names the resources being probed (Docker, Ollama, sandbox) and the word 'again' hints at a re-scan, but it never states the action concretely — re-detect, re-validate, or refresh setup state. It also fails to distinguish this from the sibling bitpull_setup_status, which presumably reports the same three components.

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?

'Look again' weakly implies re-running after something changed, but there is no statement of when to call this versus bitpull_setup_status or bitpull_install, no preconditions, and no exclusions. The agent must guess the trigger condition.

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