List the roles on a DataLens workbook

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral trait not in the annotations: 'auto-paginated', telling the agent it need not hand-roll paging. It does not disclose the inherited-bindings behavior, which the schema carries instead.

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 compact sentence with no waste, and the core purpose is front-loaded. The trailing 'auto-paginated' earns its place, though the sentence is terse enough to border on under-specification for a three-parameter tool.

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 read-only list tool with full schema coverage and read-only annotations, the description is adequate but thin: it does not mention the inherited-bindings capability or the configured max-items cap, and there is no output schema to explain return shape.

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 three parameters (limit, workbook_id, get_inherited_bindings) are documented in the schema itself. The description adds no parameter-level meaning beyond what the schema already provides, 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?

States a specific resource and data (roles on a workbook) in a compact verbless phrasing. An agent can tell it apart from the sibling datalens_workbooks_access_bindings_update (list vs update), but the phrasing 'Who has which role' is looser than an explicit 'List access bindings'.

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, when-not-to-use, or alternative is named. The relationship to the parallel update tool and to the inherited-bindings option is left entirely for the agent to infer from the schema.

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