avanan_list_msp_users

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

No annotations provided, so the description carries full burden. It only states 'List all MSP users,' which implies a read operation but provides no details about pagination, rate limits, authentication, or side effects. The scrollId parameter hints at pagination, but the description does not disclose this behavioral trait.

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 very short (one sentence) but lacks informative content. It is not verbose, but it is under-specified, missing context about pagination and return values. It earns a 3 as it is concise but insufficient.

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?

Given the simplicity (one optional parameter, no output schema), the description should at least mention that results are paginated or that it returns a list of users. The description only restates the tool's purpose, leaving the agent uninformed about important context like the need for scrollId or the structure of the response.

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?

Input schema coverage is 100% with the scrollId parameter having a description in the schema. The tool description adds no additional context for the parameter. Baseline of 3 is appropriate as the schema already documents meaning.

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 states 'List all MSP users,' which clearly indicates the tool lists all MSP users. It adds the word 'all' to distinguish from getting a single user (sibling avanan_get_msp_user). However, it is essentially a restatement of the tool name with minimal added value.

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 on when to use this tool versus alternatives. For example, it does not mention that for a single user one should use avanan_get_msp_user, or when pagination might be needed. Context is only implied by the name.

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