sigma_list_all_members

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds valuable behavioral context beyond annotations: it automatically follows pagination, meaning the agent can expect a complete result set without manual pagination loops. This is a meaningful disclosure for a list operation.

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?

The description is a single, front-loaded sentence: 'List ALL members in the organization, automatically following pagination.' Every word contributes meaning, with no fluff or repetition. It captures the purpose and key behavioral nuance in an extremely compact form.

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 zero-parameter, read-only listing tool with an output schema present, the description covers everything needed: scope (all members in the organization) and a pivotal behavior (automatic pagination). There is no additional context that would be expected, and the output format is presumably documented by the output schema.

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?

With zero parameters, the schema is fully self-explanatory. The description adds no parameter information (and doesn't need to), so the baseline of 4 for no-parameter tools applies. The absence of parameters is clear from the input schema, and the description correctly focuses on behavior.

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 description specifies a clear verb ('List'), a resource ('members in the organization'), and a scope ('ALL'), instantly differentiating from sibling tools like sigma_list_team_members and sigma_list_members. The emphasis on 'automatically following pagination' further distinguishes this as the comprehensive listing tool.

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 states when to use this tool: when you need all members and want pagination handled automatically. It doesn't explicitly mention alternatives or exclusions, but the 'ALL' and 'automatically following pagination' signals provide clear context that this is for exhaustive retrieval rather than a page-based or scoped listing.

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