pull

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

No annotations, so the description carries the full burden. It discloses the core effect (materialising a cloud node locally and attaching it to an initiative), but says nothing about idempotency, what happens if the node already exists locally, permission/auth requirements, or the return value.

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?

Two sentences, front-loaded with the verb and resource, then the multi-cloud caveat. Little waste; the 'recall mechanism' framing adds context without bloat.

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 no-annotation, no-output-schema mutation tool, the description covers the core flow but omits conflict/already-exists behavior, auth needs, and the local result shape. Adequate but with clear gaps.

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 100%, so all three params are already documented. The description restates that `cloud` targets a specific cloud in multi-cloud setups, adding no format or behavioral detail beyond the schema. Baseline 3 applies.

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 ('Pull a shared node from the cloud into the local vault by id, attaching it to the given initiative') with a clear directional scope. However, calling it 'the recall mechanism' risks confusion with the sibling tools `recall` and `cloud_recall`, which are not explicitly distinguished.

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?

Implies when to use it ('team knowledge you don't have locally yet'), which is useful context, but names no alternatives (`recall`, `import`, `cloud_recall`) and gives no when-not guidance. Usage is inferred rather than directed.

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