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

Annotations already indicate a non-read-only, non-destructive, open-world write, but the description adds crucial behavioral context beyond them: it is not an immediate on-chain action, it prepares an unsigned transaction, and nothing happens until the agent signs and submits. This is exactly the kind of non-obvious behavior the description should disclose.

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?

The definition is two tightly written sentences with zero wasted words. The core action is front-loaded, followed immediately by the essential workflow constraint.

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 transaction-preparing mutation tool with no output schema, the description covers the core action and the critical sign-and-submit flow. It could be slightly more complete by noting the prerequisite of being subscribed or pointing to get_my_subscribed_lists for list_id, but the essential invocation path is clear.

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?

With 100% schema description coverage, both signer and list_id are already well documented in the schema. The description mentions signer in passing, but adds no new syntax, format, or usage meaning for either parameter, which is the expected baseline when the schema does the work.

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 first sentence gives a specific verb and resource ('Unsubscribe from an open broadcast list'), which distinguishes it from group and private-message siblings. However, it does not explicitly contrast itself with the inverse sibling geode_messaging_join_an_open_list or other list operations, so sibling differentiation is only implicit.

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 clearly explains the required two-step workflow: this prepares an unsigned transaction (intent) that must be signed with geode-local-signer and submitted with geode_submit_intent. It lacks explicit when-not conditions or named alternatives, but the operational context is clear enough for an agent to invoke it correctly.

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