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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds the concrete result shape (id, name, email, role, job title, login/activity, lastStatus/realStatus) and the endpoint, but says nothing about result set size, ordering, or whether inactive operators are included.

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 dense sentence front-loads the action and resource, then the returned fields, then the endpoint. 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 no output schema, the field enumeration in the description does real work in telling the agent what comes back, which is the main completeness requirement here. Minor gap: no indication of whether the list is paginated, ordered, or includes deactivated operators.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals that no filtering arguments are accepted by implying an unfiltered 'list all'.

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 and resource ("List all operators (team members) of the Chaport account"), clarifies the domain term operator = team member, and enumerates the returned fields plus the underlying endpoint GET /operators. It doesn't explicitly contrast with the sibling chaport_get_operator, though the name pair makes the singular/plural distinction reasonably inferable.

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?

Usage is only implied by "List all operators of the Chaport account" – an agent can infer this is the bulk-fetch counterpart to chaport_get_operator, but nothing is stated about when to prefer one over the other or any prerequisites. No alternatives or exclusions are named.

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