security-get-role-member

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

readOnlyHint=true already declares the safe-read profile, so the description needn't repeat it. Beyond that, the description adds nothing: it doesn't state whether results are paginated, how large member lists behave, or what shape the members take. For a list tool with no output schema, that is a real gap.

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, front-loaded sentence with zero waste. It is arguably terse relative to a 5-parameter tool, but nothing in it is redundant or buried.

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 a fully documented schema and a readOnly annotation, the description only needs to round out usage and result expectations. It supplies neither, leaving the agent without guidance on recursion defaults or output shape, though the schema carries most of the calling burden.

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%, so all five parameters (identity, recurse, roleOnly, userOnly, full) are already documented in the schema, including the notable 'very large, diagnostics only' warning on full. The description repeats none of this, 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 and resource ('Get members of a Sitecore role'), which separates it from security-get-role (the role itself) and security-add-role-member / security-remove-role-member (mutations). However, it never names those siblings or clarifies the distinction explicitly, so it falls 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?

No when-to-use guidance, no prerequisites, and no alternatives mentioned. An agent must infer from the name alone that this is the read counterpart to add/remove-role-member and distinct from get-role.

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