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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the Rep Group scoping restriction and clarifies this is a POST-based read query, which is valuable, but says nothing about pagination limits or rate behavior.

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?

Three short clauses, front-loaded with the operation and scope, with zero filler. Every element (fields returned, account scope, endpoint) conveys distinct information.

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 no output schema, naming the returned fields is a useful compensation, and the account-scope constraint clarifies access. For a 5-optional-parameter paginated list tool it is nearly complete, though it could note pagination defaults.

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 80%, so the schema already documents name, offset, page_size, and sort_direction. The description adds no parameter detail beyond what the schema provides; the fields it lists are return fields, not input parameters. Baseline 3 is appropriate.

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?

States a specific verb (List) and resource (Rep Group's salespeople), and names the returned fields (name, abbreviation, status, ids). No sibling tool covers salespersons, so it is inherently distinguishable, but it does not explicitly differentiate itself from the broader list_* family.

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?

'Rep Group accounts only' gives a clear applicability constraint, which is useful. However, there is no explicit when-to-use vs. alternative guidance, and no mention of what to do for non-Rep-Group accounts.

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