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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that results are people plus the projects they work on and that people are ranked by activity, which is useful, but it does not explain how area and query interact or what the returned records contain.

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?

The description is compact and front-loads the main behavior before giving the use case. One sentence is long and packs multiple concepts, but there is no filler.

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 description does carry the burden of explaining returns, and it does state that people come with their projects. However, it omits what happens when both area and query are supplied, how activity is measured, and the shape of results beyond names and projects.

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 coverage is 67%, with limit and query already documented in the schema. The description usefully repeats the area enumerations and clarifies that query selects projects by matching words, but it adds little beyond the schema for the other parameters.

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 resource (people most active in projects) and scopes it by area or query, and it adds a clear use case ('find who to ask about a part of CKB'). It does not explicitly distinguish itself from siblings such as find_projects or person, 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?

The phrase 'Useful to find who to ask about a part of CKB' gives implied usage context, but there is no guidance on when to use this instead of find_projects, person, or project. The agent must infer the boundary.

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