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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety and repeatability are covered. The description contributes nothing beyond that: no statement about pagination, result size, ordering stability, or what a returned identity contains.

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 this is under-specification rather than conciseness: a single fragment that omits the verb and resource. There is no wasted clause, but there is also almost no information, so brevity is not earning its place.

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 directory-listing tool with three parameters, no required fields, and no output schema, the description omits what an identity record is, that results are paginated, and how ordering interacts with cursor traversal. Annotations cover safety only; behaviorally the agent is left guessing.

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 sort/limit/cursor are fully documented in the schema, including the 50 clamp and the meta.next_cursor provenance. The description's "karma or recent activity" loosely echoes the enum ("active" vs "recent activity") but adds no syntax or default detail. 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?

"The directory, by karma or recent activity." is a noun fragment with no verb and never names the resource (identities/users). It gestures at a listing sorted by karma or activity, but an agent cannot confidently distinguish it from commons_whoami, commons_profile_get, or commons_search on this text alone.

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 explicit when-to-use statement and no mention of alternatives. The only steer is the sorting choice, which the schema enum already supplies. It implies browsing rather than targeted lookup, but nothing states when to prefer this over commons_profile_get or commons_search.

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