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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value beyond that by disclosing the membership definition and the return payload shape ('ids and emails'), which the annotations cannot convey. It does not mention pagination or ordering, hence not 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?

Two short sentences, zero filler. The scope definition is front-loaded and the actionable 'use the id for set_kanban_assignee' instruction closes it. 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?

For a parameterless read tool with no output schema, the description supplies everything needed: who is returned, why they qualify, and the field to carry forward to set_kanban_assignee. Nothing an agent needs to call it correctly is missing.

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?

There are zero parameters, and the schema is empty (additionalProperties: false), so the 4 baseline applies. The description correctly implies no filtering arguments are needed and instead explains what the caller should do with the output.

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 the specific resource (board members) and defines its scope precisely as 'the publisher and the teammates with kanban access', plus the roles they can hold (assignee, watcher, mention). That is far more informative than a bare tautology. It stops short of explicitly differentiating itself from siblings like get_kanban_board or list_kanban_projects, so a 4 rather than 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 gives clear downstream context: 'use the id for set_kanban_assignee', which tells the agent why and when it would call this tool. There are no explicit exclusions or when-not conditions versus sibling list/get tools, so it falls just short of a 5.

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