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

Annotations declare a non-read-only, open-world, non-destructive write, and the description goes meaningfully beyond that by explaining the two-phase intent model — nothing executes until signing and submission. It adds real context the annotations cannot express, but does not mention permissions, failure modes, or whether joining is reversible.

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 with the action front-loaded and the transaction caveat immediately after. The second sentence is dense but every clause (unsigned, intent, signer, sign, submit) carries needed 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 chain-writing tool with no output schema and no annotations covering the intent workflow, the description supplies the essential lifecycle the agent needs. It could say more about what the prepared intent returns or any prerequisites (e.g., group membership rules), but the critical mechanics are present.

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%, so both parameters are already documented in the schema and the baseline is 3. The description reinforces what `signer` means in the transaction flow but adds no syntax or format detail beyond the schema.

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 ("Join a messaging group") that is plainly distinct from siblings like geode_messaging_join_an_open_list and geode_messaging_make_a_new_group. It does not explicitly name those siblings to draw the contrast, so it stops short of a 5.

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?

Gives clear operational context: this only prepares an unsigned intent, and the caller must sign with geode-local-signer and submit via geode_submit_intent. That effectively names the required follow-up tools, though it offers no explicit when-not guidance.

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