List Space Group Members

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuine behavioral fact beyond that — every page consumes API quota and all_pages is bounded — which is useful for an agent planning pagination. It stops short of describing return shape, ordering, or error/auth behavior.

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?

Very short, but the opening sentence duplicates the title verbatim and earns no space, and the remaining fragments are telegraphic rather than structured. It is front-loaded in the sense that there is almost nothing to load.

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 7-parameter, paginated list tool with no output schema, the description covers the quota/pagination caveat but says nothing about what a member record contains, ordering, or continuation handling. Annotations and the fully documented schema fill most of the gap, making this minimally adequate rather than 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 description coverage is 100%, so the schema already documents all 7 parameters including all_pages boundedness and max_items continuation state. The description's mention of bounded all_pages and quota merely echoes what the schema states, adding no syntax or semantics beyond it. Baseline 3 applies when the schema carries the load.

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 "List Space Group Members" only restates the tool name/title, adding no verb+resource detail. "Reads community data" adds operational flavor but does not distinguish it from close siblings like list_space_members or list_space_group_members-adjacent list tools. Purpose is inferable but not sharpened beyond the name.

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 indication of when to use this tool versus list_space_members, get_space_group_member, or list_space_groups. The only guidance-like content is pagination mechanics, not selection criteria or prerequisites.

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