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 and the description owes less. Beyond those, it adds only the raw endpoint (GET /users), which even conflicts slightly in naming with "customers"; it says nothing about ordering, pagination flow, rate limits, or what a page contains. Nothing behavioral beyond the structured fields.

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 terse fragments with no waste, but the terseness comes at the cost of specification rather than being disciplined brevity. The parenthetical definition is front-loaded and helpful; the endpoint string adds little for an agent.

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?

For a paginated list tool with no output schema, the description should at least say what a page returns and that iteration is via offset/next_offset. It omits ordering, total-count behavior, and any return-shape hint, leaving the agent to discover pagination semantics from the schema alone.

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?

Both parameters are fully documented in the schema (100% coverage), including the 1-100/default-25 limit and the instruction to pass next_offset into offset. The description adds no parameter detail, which is acceptable at full schema coverage, so the baseline 3 applies.

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?

Names the resource implicitly ("Registered customers") and adds a useful gloss ("the account's buyers"), which distinguishes registered account buyers from anonymous/guest purchasers. But it never uses a verb like "list" or states the scope of the listing, so the operation is inferred from the name and title rather than stated. It also does not differentiate itself from the sibling sellasist_get_customer (single customer).

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?

There is no when-to-use guidance at all: no mention of when to prefer this over sellasist_get_customer, no prerequisites, no note to paginate. The endpoint reference "GET /users" is the only hint of context. An agent must infer usage entirely from the tool name.

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