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

Annotations confirm a non-read-only, open-world write, and the description adds genuinely non-obvious behavior: nothing is committed until the returned intent is signed and submitted. It does not mention fees, rate limits, or name-collision behavior, but the intent-flow disclosure is the key nuance.

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 dense sentences: the purpose first, then the write/sign/submit constraint. No filler, and the most important behavioral caveat is front-loaded.

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 mutation tool with no output schema and no annotation detail beyond hints, the description covers the critical fact that this is a two-step intent flow. Minor gaps remain around the undocumented hide_from_search parameter and any limits on list creation.

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 coverage is 75% and the schema already documents signer, description, and new_list_name in detail. The description only mentions `signer`, which is already explained in the schema; `hide_from_search` remains undocumented in both places.

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: 'Create an open broadcast list that others can subscribe to.' An agent can distinguish this from geode_messaging_make_a_new_group by the list/subscribe framing, though no sibling is named explicitly.

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 a clear procedural context: it prepares an unsigned intent for `signer`, which must be signed with geode-local-signer and submitted with geode_submit_intent. This tells the agent exactly what happens next, though it doesn't contrast when to pick a list over a group.

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