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

No annotations exist, so the description carries the burden. It does add real behavioral context – the rank is not writable from this tool, and for Simafri Suite clients rank is held remotely and restated at sign-in – which is genuinely useful. But it omits return shape, ordering, pagination, and permissions, leaving gaps for a no-annotation tool.

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?

It is short, but the sentences are dense and metaphorical ('how far they see into the mail', 'held at the shop'), requiring re-reading. The key fact – that this lists people and their queue scope – is not front-loaded in plain language.

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 annotations and no output schema, the description is the only source of return-value detail; it names the fields (sign-in, rank, queue visibility) but gives no structure, ordering, or pagination guidance. Adequate to call, but not complete for interpreting results.

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's discussion of return fields is extra value rather than parameter semantics.

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 and resource ('Lists everyone on the account') and enumerates what is returned: sign-in method, rank, and queue visibility. It is distinguishable from siblings like list_teams or list_contacts, but the jargon ('works_every_queue', 'the shop', 'Simafri Suite') makes the scope harder to grasp than it needs to be.

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 implied rather than stated: 'It says who works where, never what any of it holds' bounds the tool to membership/organizational data, which implicitly steers an agent away for content questions. However, no sibling is named as an alternative and no prerequisites or exclusions are given.

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