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

Annotations only mark it as a non-read-only, non-destructive open-world write. The description adds the crucial behavioral fact that nothing is committed on-chain until a separate sign/submit cycle, which an agent must know to sequence calls correctly. It stops short of stating cost, finality, or what membership state results.

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 tight sentences, front-loaded with the action and immediately followed by the commit/signing constraint. No filler or redundant restatement of the title.

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 2-parameter mutation with full schema coverage and no output schema, the description supplies the essential missing piece: the intent/sign/submit lifecycle and the naming of the follow-up tools. It does not describe the resulting subscription state or any prerequisites for the list being open, which keeps it just short of complete.

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% and both parameters (signer, list_id) are fully documented in the schema. The description restates the role of `signer` in the signing flow but adds no new format or constraint detail, so the baseline of 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 and resource ('Subscribe to an open broadcast list'), which clearly separates it from geode_messaging_unsubscribe_from_open_list and from the group siblings like geode_messaging_join_a_group. An agent can identify the operation without opening the schema.

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?

Explains the two-step workflow explicitly: this only prepares an unsigned intent, which must then be signed with geode-local-signer and submitted with geode_submit_intent. That is strong actionable context, though it gives no when-not guidance (e.g. joining a closed/paid list or a group).

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