Get Space Permissions

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

ReadOnlyHint=true already signals a read operation. The description adds useful behavior beyond that: it names the exact endpoint, discloses the Cloud-only restriction, and describes the returned structure as a results list with principal, operation, and target. No contradiction with annotations.

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 compact, front-loaded with the core purpose, and every sentence adds value: endpoint, Cloud caveat, return shape, and intended use. There is no filler or redundancy.

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 readOnlyHint, full parameter descriptions, an output schema, and a description of the returned permission object shape, the definition is complete for safe and correct invocation. The Cloud-only note prevents a common failure mode.

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%, with space_id explained in detail including how to find it. The description itself adds no parameter-level semantics beyond the schema, so the baseline of 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?

The first sentence states a specific verb and resource: 'List all permission assignments for a Confluence space.' The description also names the wrapped endpoint and the audit use case, making it easy to distinguish from page-level restriction tools like confluence_get_page_restrictions.

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 clear context: use it to audit who has access to a space, and explicitly notes it is only available for Confluence Cloud, warning that Server/Data Center instances use different permission APIs. It does not name sibling alternatives, but the when-to-use and when-not-to-use are stated.

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