Get Page Restrictions

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

The annotation readOnlyHint=true already identifies this as a read operation, and the description adds value by explaining that it returns 'current restriction lists' and that an empty list means unrestricted. This gives the agent important interpretation context beyond the annotation, though it does not discuss pagination, authentication, or other edge cases.

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 two sentences, front-loading the purpose and then adding a key interpretation detail. Every word earns its place, and there is no redundancy or filler.

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?

The tool has one parameter, a clear read-only annotation, an output schema, and a description that explains the return semantics (restriction lists and empty list meaning). This is sufficient for an agent to select and invoke the tool correctly without ambiguity.

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?

The schema covers 100% of parameters with a clear description ('The ID of the page'), so the baseline is 3. The description does not add further meaning to the page_id parameter, but also does not need to since the schema is sufficient.

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 uses a specific verb ('Get') and resource ('view and edit restrictions for a Confluence page'), clearly distinguishing it from sibling tools like confluence_set_page_restrictions and confluence_check_content_permissions. It also clarifies the two operations (read/view and update/edit).

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 implies usage (to retrieve current restrictions) but does not explicitly state when to use this tool versus alternatives such as confluence_set_page_restrictions or confluence_check_content_permissions. There are no exclusion criteria or alternative recommendations, leaving the agent to infer from context.

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