Share a fleet's current member hosts with users or roles

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

The description discloses significant behavioral aspects beyond annotations: it grants hostAccess to all current member hosts at the time of sharing, and hosts added later are not automatically shared. This snapshot semantics and non-propagation detail add value beyond the sparse annotations.

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 sentences: the first states the core purpose, the second delivers the critical snapshot and re-run caveat. There is no filler, and the most important behavioral detail is front-loaded.

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?

While the purpose and snapshot behavior are clear, the description lacks essential parameter semantics and does not mention what the call returns or any prerequisites. Given four parameters with zero schema descriptions and no output schema, this leaves too many gaps for reliable invocation.

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?

With 0% schema description coverage, the description must explain the parameters, but it only mentions that targets are users or roles. It does not clarify id (presumably fleet ID), durationHours, permissionLevel, or the structure/format of targets, leaving an agent unable to construct a valid request.

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 clearly states the action: sharing a fleet's current member hosts with users or roles. It uses a specific verb ('Share') plus resource ('fleet's current member hosts') and recipients ('users or roles'), and it is unique among the sibling tools which do not include another sharing operation.

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 description gives clear context for when to use the tool: to share current members at snapshot time, and it explicitly instructs that re-running extends sharing to later-added hosts. It does not name alternatives, but no direct sibling sharing tool exists, making this guidance sufficient for selection.

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