swarm_join_tokens

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. Description adds value by detailing that tokens are read from swarm.attrs['JoinTokens'] after a reload, ensuring freshness, and warns about treating output as sensitive and avoiding logging.

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?

Three sentences, efficiently organized. Front-loaded with purpose, then usage context and security note. No redundant 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?

Despite lacking an output schema, the description fully documents the return value structure and behavioral details. No parameters to document. Complete for a simple read-only tool.

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?

No parameters; baseline 4. Description adds meaning by documenting the return format (dict with Worker and Manager keys) and emphasizing tokens are secret bearer credentials.

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 it returns swarm join tokens, with specific verb 'Return' and resource 'swarm join tokens'. It distinguishes from siblings like swarm_join and swarm_init by explaining the token's role in the init-to-join flow.

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 explains when to use: after swarm_init, to obtain tokens for swarm_join. It notes that without a token, swarm_join cannot be called, closing the loop. Security sensitivity is mentioned but no explicit when-not-to-use.

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