list_all_users

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds key behavioral context: 'Enterprise-gated. Returns 403 on non-Enterprise Portkey plans', which is beyond annotations and critical for agent awareness.

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?

Two concise sentences. First front-loads purpose and resource, then provides usage guidance and constraints. No wasted words.

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?

Covers purpose, return fields, usage guidance, alternatives, and enterprise constraint. Output schema exists, so return format is already detailed. Complete for a list tool.

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% with descriptions for both parameters. Description does not add extra parameter details, but baseline is 3 since schema already covers meaning adequately.

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?

Clearly states 'List accepted org users with id, name, email, role, and timestamps', specifying the verb and resource. Distinguishes from sibling tools like list_user_invites and mentions usage context for get_user, update_user, etc.

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?

Explicitly tells when to use: 'find a user_id before get_user, update_user, delete_user, or add_workspace_member' and points to alternative 'use list_user_invites for pending invitations'. Also notes enterprise gating and 403 error on non-Enterprise.

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