AtlaSent — List SCIM Users

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral context: compliance with SCIM 2.0, support for filter expressions and pagination (startIndex/count). No contradiction.

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 that front-load the core purpose and add essential details. No unnecessary 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?

The description covers the tool's purpose, standard, and parameters well. However, it does not mention the return format (e.g., list of user objects in SCIM format). Given no output schema, describing the response structure would improve completeness.

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?

All 4 parameters are well-described in the schema (100% coverage). The description adds value by providing examples of SCIM filter syntax and mentioning pagination behavior, enhancing understanding beyond the schema.

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 clearly states it lists SCIM users for an organization, referencing the SCIM 2.0 standard and RFC 7643. It distinguishes from sibling tools like get_scim_user (single user), create/delete/patch, and list_scim_groups by specifying it's for listing provisioned users with filtering and pagination.

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 provides clear context for when to use this tool (listing provisioned users) and hints at syntax (filters, pagination). However, it does not explicitly mention when not to use it or alternatives like get_scim_user for single user retrieval.

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