Get authorized users

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

The readOnlyHint=true annotation already declares the safety profile, and the description's 'List' verb is consistent with it. The description adds scoping context ('per partner', 'message sender authorization') but discloses nothing about response format, grouping, or pagination behavior. With annotations covering safety, a 3 is appropriate.

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?

A single nine-word sentence that front-loads the verb and resource and packs scoping context into a parenthetical. Every word earns its place; there is no filler or repetition.

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?

With five undocumented parameters, no output schema, and only a readOnly annotation, the description leaves the agent to guess at response shape and how partner scoping is requested. Adequate for a simple read-only list endpoint, but a sentence on response format and filter semantics would close the gap.

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 description coverage is 0%, so the description must compensate for the five undocumented parameters, but it mentions none of them. Parameter names (top, skip, filter, select, orderby) hint at OData-style paging and projection, yet the agent gets no guidance on how filter/select apply to authorized-user listing or how 'per partner' scoping is expressed.

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 ('List') and resource ('authorized users') and scopes it with 'per partner' and the clarifying parenthetical '(message sender authorization)', which helps distinguish it from close siblings like get_partners and get_user_credentials. It doesn't explicitly name alternatives, so it stops short of a 5.

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 phrases 'per partner' and 'message sender authorization' imply the use case: checking which users are authorized to send messages on behalf of a partner. However, there is no explicit when-to-use guidance, no exclusions, and no mention of when to prefer siblings such as get_user_credentials.

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