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

Annotations already declare readOnlyHint and destructiveHint=false, so 'read-only' is largely redundant. However, 'no signature' is genuine auth-context disclosure the annotations do not carry — it tells the agent no wallet signing flow is required — and the pagination defaults are restated for quick scanning.

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, purpose front-loaded, then auth note, then pagination. The pagination sentence duplicates values already in the schema and could be trimmed, but nothing is padded and the ordering is sensible.

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?

With no output schema, the description should say something about what a returned group contains or its ordering, but it only says results are paginated. The core call is answerable, yet the agent cannot anticipate the response shape.

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 all three parameters are already documented with defaults and bounds. The description adds only the meaning of `caller` ('account whose view to read', caller-dependent results) and repeats limit/offset values, which does not exceed the schema's own detail.

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: list the messaging groups `caller` belongs to. That is clear enough to act on, but it does not distinguish itself from the very similar sibling `geode_messaging_get_my_inbox_groups` (nor from `find_groups_by_keyword` or `get_my_subscribed_lists`), leaving the agent to guess which 'my groups' variant applies.

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?

There is no explicit when-to-use statement and no named alternative. The description hints that `caller` selects 'caller-dependent results', but nothing tells the agent when to prefer this over `get_my_inbox_groups` or when to use `find_groups_by_keyword` instead.

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