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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond that: results are scoped to the caller's own company and the payload is limited to name, email and role, all of which members already see — a useful data-minimization disclosure. It stops short of describing ordering or result size.

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 short sentences, front-loaded with the scope and payload disclosure, with no filler. The opening sentence is a verbless fragment, which slightly weakens readability but costs no 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?

For a zero-parameter, read-only list tool with no output schema, the description covers the essentials: whose data, what fields, and what the ids are for. Missing only minor operational detail such as ordering or whether the full list is returned unpaged.

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 no parameters, so the baseline is 4. The description correctly implies no filtering or paging inputs, consistent with the empty schema, and adds no misleading parameter expectations.

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 identifies the resource precisely — 'the people in the caller's company' — and even explains the practical value of the result (ids used to name an assignment's assignee). It lacks an explicit verb like 'list', so the operation is implied rather than stated, and no sibling is named for contrast.

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: the mention of 'the ids an assignment's assignee is named by' hints that this is the lookup for resolving assignee references. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative among the many erp_list_* siblings.

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