List Space Members

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world. The description adds genuine value beyond them by warning that every page counts against the API quota and that all_pages is bounded rather than a complete snapshot. It stops short of describing return shape or rate-limit specifics.

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 short sentences, front-loaded with the purpose and then the quota caveat. No filler, though the second sentence ('Reads community data') is near-tautological for a list tool and earns little.

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 read tool with no output schema, the description covers the quota/pagination cost but says nothing about what a member record contains, ordering, or how it differs from the many sibling member-listing tools. Annotations carry the safety profile, so the remaining gap is moderate.

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 every parameter is already documented in the schema. The description reinforces the all_pages/quota tradeoff but adds no syntax, defaults, or format detail beyond what the schema states, which is the expected baseline of 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+resource (list space members) and adds that it reads community data, so the agent knows the domain. It does not explicitly distinguish itself from near-siblings like list_members or list_space_group_members, so it falls short of a 5.

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?

The description only notes that all_pages is bounded and paginated consumption of quota. There is no statement of when to use this tool versus list_members, list_space_group_members, or get_space_member, and no prerequisites or exclusions.

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