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

Goes well beyond the destructiveHint/readOnlyHint annotations by disclosing that this writes to the chain, that nothing happens until the intent is signed and submitted, that the operation is irreversible, and that a confirm_token round-trip is required. This is exactly the behavioral context an agent needs before invoking a destructive on-chain mutation.

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?

Three tight sentences with no filler: the action and scope come first, the on-chain/signing consequence second, and the irreversibility/confirm requirement last. Every clause carries decision-relevant 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 destructive, no-output-schema mutation tool, the description supplies the prerequisite signing workflow, the irreversibility warning, and the multi-step confirmation path, so an agent knows both what it does and what it must do around it. Nothing decision-critical is missing.

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 100%, so the baseline is 3; the description adds value by explaining the confirm_token two-call protocol (first call returns it, second call consumes it) that the schema only names. The signer/submit relationship is restated from the schema rather than extended, keeping it out of 5 territory.

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 (delete) and a precisely scoped resource (one message you sent to a group), which directly distinguishes it from siblings like geode_messaging_delete_all_messages_to_group and geode_messaging_delete_single_message_to_account. An agent can select it 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 full flow: it prepares an unsigned transaction for `signer`, then you sign with geode-local-signer and submit via geode_submit_intent. It also describes the two-step confirm_token gate. It never explicitly states when NOT to use it or contrasts against the list/account deletion siblings, so it falls just short of a 5.

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