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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: results are permission-filtered to what the token can reach, and each entry carries the caller's role, plus an explicit scope requirement (projects:read). It stops short of describing pagination over limit/cursor.

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, front-loaded sentences with no waste; scope and result contents come before the permission note. The terseness is what creates the parameter gap, but nothing is redundant.

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?

An output schema exists and annotations are rich, so return shape and safety need not be explained. Still, for a paginated list tool with three undocumented parameters, the description leaves out paging and filtering behavior that an agent needs to call it well.

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% for three parameters (limit, cursor, search), and the description mentions none of them. It does not explain that limit caps at 200, that cursor is a pagination token, or that search filters projects by name, so an agent must infer paging semantics entirely from parameter names.

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 gives a concrete resource (projects) plus a meaningful scope qualifier: only projects 'this token can reach', and it states the payload includes 'your role in each'. That is clearly distinct from get_project or create_project, though it never explicitly contrasts with the sibling read tool.

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 'Requires projects:read' line is a real prerequisite that tells an agent whether it can call the tool at all. However there is no explicit when-to-use/when-not guidance and no pointer to get_project for single-project detail or to list_members for role listings, so selection among siblings is left implied.

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