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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Read-only' restates that. However, 'no signature' adds genuine auth context not present in annotations, and the pagination note discloses result-bounding behavior. It stops short of explaining return shape or failure modes, so a 3 is appropriate.

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 compact sentences, front-loaded with the core purpose before the read-only note and pagination detail. Every sentence carries information, though the 'Read-only' clause mildly duplicates the readOnlyHint annotation.

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 three-param read-only list tool with full schema coverage and complete safety annotations, the description covers purpose, the optional caller rationale, and pagination. The absence of an output schema means return values need not be described, so it is essentially complete.

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 all three parameters (limit, caller, offset) are documented in the schema with defaults and ranges. The description reinforces the pagination defaults and clarifies caller's purpose ('view to read'), adding marginal value but not new syntax beyond the schema, keeping it at baseline 3.

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 ('List') and resource ('open broadcast lists caller subscribes to'), which lets an agent identify the operation. It does not explicitly distinguish itself from close siblings like geode_messaging_get_my_open_lists, so an agent must infer the subscribed-vs-open distinction.

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?

No guidance on when to choose this over alternatives such as get_my_open_lists, get_my_inbox_lists, or find_lists_by_keyword. The 'caller-dependent results' note describes a parameter rather than a usage condition, leaving the agent to infer selection.

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