List Sharing Groups

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds the pagination behavior, but it does not clarify what 'sharing groups' contain, how results are ordered, or what a caller should expect in the response.

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 a single concise sentence that front-loads the action and resource, immediately followed by the key behavioral trait (paginated). There is no filler or redundant restatement beyond the title.

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 read-only list operation, the description plus annotations and fully documented parameters are largely sufficient. It could be more complete by explaining what constitutes a sharing group or how this list relates to other sharing-list tools, but the minimal context does not create a serious gap.

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 input schema fully documents both parameters ('page' with default 1 and 'limit' with default 10), so the schema carries the semantic weight. The description only reinforces that the listing is paginated, adding marginal meaning beyond the schema.

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 clearly states the action ('List') and resource ('sharing groups'), and adds 'paginated' to convey the operation's scope. It is immediately distinguishable from sibling sharing-group tools like create/get/update/delete/share, as well as related list tools.

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: when you need a paginated list of sharing groups. However, it does not explicitly mention when not to use it, nor does it point to alternatives such as lyzr_sharing_get_group or lyzr_sharing_list_accessible.

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