fleet_pull

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

With no annotations present, the description carries the full burden and handles it well by disclosing that downloads can be many GB, take minutes, and require explicit user approval. This is substantial behavioral context beyond the basic action and helps an agent avoid an expensive or unapproved call.

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?

The description is two tight sentences with no filler. The main action is front-loaded and the important warning follows immediately. 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 two-parameter tool with no output schema and no annotations, the description gives the essential invocation context: what it does, what it affects, and a significant caution. It could be more complete by mentioning output or return behavior, but the core information an agent needs to select and call it 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 description coverage is 0%, so the description must compensate. It does clarify the conceptual relationship between the two parameters: a model is downloaded onto a node. However, it does not provide format, identifier conventions, valid values, or examples for 'node' or 'model', so the compensation is only partial.

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 and resource: 'Download a model onto a node (ollama pull)'. It clearly identifies the operation and the target, and distinguishes it from sibling tools by focusing on the pull action rather than status, setup, or job management.

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 'only with the user's approval' is an explicit condition on when the tool should be invoked, which is crucial guidance for an agent. It does not name sibling alternatives, but no sibling appears to perform the same model-download function, so the omission is not a significant gap.

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