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

With no annotations and no output schema, the description carries the full disclosure burden. It usefully warns that joining runs a program on the user's computer and consumes their agent subscription, which is meaningful side-effect context, but it does not describe what invoking this tool itself returns or that it is a safe read-only lookup.

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 tightly written sentences, purpose first and the caution second, with no filler or redundancy. Nothing could be removed without losing 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?

For a simple informational tool this is close to adequate, but it omits what the tool actually returns (steps, links, prerequisites) and gives no sense of the content's shape. With no annotations or output schema to fill that gap, the description should say more about the response.

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 are no parameter semantics to explain; the empty schema is self-evident. Baseline 4 applies for a no-parameter tool.

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 identifies the topic precisely: instructions for how a person joins the lab and contributes their coding agent's time. It is clearer than the bare name, but it never states that the tool returns documentation/instructions, and it does nothing to distinguish itself from siblings like get_program or list_programs.

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 clause 'ask them first' hints that this material should be surfaced before the joining action occurs, but it never states when to call this tool versus alternatives, nor what a caller should do with the result. Usage is only implied.

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