entangled_get_swarm

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

With no annotations, the description carries the full burden, and it does disclose the shape of the returned data. However, it never states that this is a read-only/no-side-effect operation, nor anything about freshness, auth, or limits on the swarm listing. Adequate but with a real gap given zero annotation coverage.

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, zero filler, and the core purpose is front-loaded before the usage hint. Every clause carries information.

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?

Zero parameters and a full output schema mean the description needn't explain return values, and it correctly stays high-level while naming the fields available. What's missing is any statement of the operation's read-only nature, which no annotation supplies.

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 there is nothing for the description to disambiguate; the schema is trivially complete at 100% coverage. Baseline 4 applies since no parameter guidance is needed.

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 states a specific verb ('Discovers') and resource ('all active agent CLIs in the entangled swarm') and enumerates the fields returned (client type, workspace, heartbeat, task), so an agent knows exactly what it retrieves. It does not, however, differentiate itself from the similar-sounding sibling entangled_get_activity_feed, which also surfaces agent activity.

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?

'Use this to see who else is working' gives a clear when-to-use context, which is better than nothing. But it offers no exclusions or alternatives, so an agent choosing between this and entangled_get_activity_feed (or entangled_list_locks) gets no routing help.

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