ise_ers_list_internaluser

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'Paginated' which is useful, but doesn't state return format, page size defaults/limits, whether this is a safe read operation, authentication needs, or performance implications. For a list operation with no annotations, more behavioral context is expected.

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?

Extremely concise two-sentence description with zero waste. It front-loads the primary purpose. However, given the tool's relative simplicity, more behavioral detail could have been packed in without becoming verbose. It's efficient but arguably under-specified rather than optimally concise.

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?

A paginated list tool with no annotations, no output schema, and no pagination parameters documented in the schema (page/size have no descriptions). The description only says 'Paginated' without explaining page/size defaults, max values, or how to page through. Given the tool's simplicity this is borderline adequate but the pagination gap is a real shortfall.

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 only 33% (deployment is described, but page and size are not). The description adds the pagination behavior ('Paginated') which gives meaning to page/size, and the deployment param already has a rich schema description. The description partially compensates for the 67% schema gap by signaling pagination semantics.

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 'List all Internal Users. Paginated.' clearly states the verb (List) and resource (Internal Users), and distinguishes this from sibling tools like ise_ers_get_internaluser (single retrieval) and ise_ers_search_internaluser (filtered search). The pagination note adds scope clarity. However, it doesn't explicitly contrast with search_internaluser to reinforce the 'all' scope versus filtered.

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?

There is no guidance on when to use this tool versus the sibling search tool (ise_ers_search_internaluser), get tool, or other list tools. The pagination mention implies large-result scenarios but no explicit exclusions or alternative recommendations. No prerequisites or context given about deployment requirements beyond the 'deployment' param schema description.

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