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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only 'visible' (results are permission-filtered) and the read-access precondition, but says nothing about pagination behavior or result ordering.

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?

A single tight sentence with zero filler, and the scope (space) is front-loaded. It is efficient, though arguably so terse that it leaves the members/memberships distinction unaddressed.

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 simple, fully annotated, well-described-schema read tool this is close to sufficient. The gaps are the members vs memberships wording and the absence of any mention of paginated results, which the description cannot defer to an output schema since none exists.

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% and all four parameters (view, limit, space, cursor) are documented in the schema itself. The description adds no format, default, or constraint detail beyond that, so the 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?

States a specific verb (List) and resource (members of a space), so the operation is unambiguous. However it says 'members' while the tool is named list_memberships, and it never distinguishes itself from the sibling manage_membership, so an agent must infer the read-vs-manage split.

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?

'of a space you can read' is an implicit precondition that usefully signals the read-access requirement. There is no explicit when-to-use or when-not-to-use guidance and no mention of the obvious alternative (manage_membership) for mutation, leaving usage implied rather than stated.

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