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

With no annotations provided, the description carries the full burden and does well: it discloses that the endpoint is public with no API key required, that data is sanitized of internal IDs, and that it draws from a persistent (not one-shot) population. It omits freshness/rate-limit behavior, which keeps it from a 5.

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?

Purpose is front-loaded in the first sentence, followed by usage context, an auth note, and a compact returns block. Every sentence carries information, though the returns enumeration is dense and could be trimmed if an output schema existed.

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?

There is no output schema, but the description compensates with an inline 'Returns' shape covering population totals and per-agent fields. Combined with the public-access note and sanitization disclosure, an agent has enough to call and interpret it correctly.

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 100%, so the lone 'limit' parameter (range 1-60, default 20) is fully documented in the schema. The description adds no additional meaning about sampling size or its effect, so the baseline of 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?

The description names a specific verb and resource ('Browse the persistent CrowdOS crowd — a sample of the live agent population') and adds a distinguishing property (sanitized of internal IDs). It does not explicitly contrast itself with siblings like list_demographic_presets or estimate_reach, so it stops short of a 5.

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?

It offers a soft use case ('useful for showing what kind of people are in this audience to a user') but gives no when-not guidance and does not name an alternative sibling for related needs such as demographic enumeration. Usage is implied rather than prescribed.

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