avanan_get_msp_user

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

No annotations are provided, so the description carries the behavioral burden. 'Get' conveys a read-only, non-destructive operation, but the description does not disclose potential error behavior, required permissions, or response characteristics. This is adequate for a simple lookup but not especially rich.

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 a single, direct sentence with no filler or redundancy. It front-loads the action and resource, and every word contributes to understanding the tool's purpose.

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?

This is a simple, one-parameter tool with no output schema, no enums, and no nested objects. The description plus schema provide enough information for an agent to invoke the tool correctly. The only minor gap is the lack of an explicit statement about return value or not-found behavior, but the simplicity keeps this from being a major deficiency.

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?

The schema already documents the single parameter with 100% coverage ('user_id' described as 'MSP user ID.'). The description adds little beyond restating that the fetch is by ID, which is acceptable since the schema carries the semantic weight.

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 a specific verb ('Get'), a clear resource ('a single MSP user'), and the lookup criterion ('by ID'). It clearly distinguishes this from sibling tools like avanan_list_msp_users (plural/all) and avanan_update_msp_user (mutation).

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 implies the appropriate use case: retrieve exactly one MSP user when the ID is known, as opposed to listing all users. It does not explicitly name alternatives or exclusions, but the 'single ... by ID' wording provides clear context for when to invoke this tool.

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