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

ReadOnly, idempotent, and non-destructive behavior is already declared by the annotations, so the bar is lower. The description adds the ranking and filtering behavior, but leaves out pagination behavior, cursor semantics, open-ended result expectations implied by openWorldHint, and default filtering like leaderOnly.

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 only two sentences, front-loads the action and outcome, and provides the most relevant filtering context in a compact form. Every clause earns 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?

Given the 16-parameter surface and no output schema, the description is under-complete. It does not describe return shape, pagination (cursor/pageSize), how scoring limits work, or the default leaderOnly filter, leaving an agent to inspect the schema or discover behavior at runtime.

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 0%, so the description carries the full burden for explaining 16 parameters. It only sketches a few filter dimensions (rep, tag, rating, status, bot/insider) and omits or leaves ambiguous the meaning of minScore/maxScore, search, cursor, pageSize, and the default leaderOnly behavior. This is not enough to compensate for the lack of individual parameter descriptions.

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 clearly states a specific action ('Rank'), a precise resource ('the most engaged members of a project'), and the ranking basis ('by engagement percentile'). It also differentiates itself from sibling list tools by emphasizing leadership/engagement and the filtering dimensions.

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 description gives an explicit use case ('Use when you need who is paying attention right now') and lists relevant filter axes. However, it does not explicitly contrast this with sibling tools like sm_list_members or sm_list_at_risk, so the 'when not to use' guidance is absent.

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