get_all_users

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

Annotations are absent, so the description carries the full behavioral burden, and it discloses nothing beyond the generic read verb 'Get'. It does not mention pagination for potentially large result sets, whether 'all users' includes suspended or hidden users, how results are ordered, or any permission requirements tied to zoid.

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?

Five words with zero filler: the verb leads, the resource and scope follow, and the sentence ends cleanly. Nothing could be removed without losing meaning, and nothing extraneous is present.

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 simple single-parameter list operation with an output schema present, the description is minimally adequate. The main gaps are operational: no pagination handling, no clarification of what 'details' means relative to get_user_details, and no indication of where zoid originates.

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 0%, so the description must compensate, but it only weakly implies that zoid identifies an organization through the phrase 'organization users'. It never explicitly defines zoid, explains where to obtain it, or describes how it scopes the returned users.

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 uses a specific verb ('Get') and resource ('all organization users'), clearly stating this is a bulk retrieval of users in an organization. The 'all' qualifier distinguishes it from get_user_details (single user). However, 'details' is vague about which user attributes are returned, and no distinction is made from the sibling get_all_accounts, which could overlap conceptually with 'users'.

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 is given about when to use this tool versus its many siblings, such as get_user_details for a single user, get_all_accounts for accounts, or get_organization_details for org-level information. The only hint—the word 'all' implying bulk retrieval—comes from the tool name itself, so the description adds no independent usage direction.

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