List what DataLens entries use or are used by

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=true, so safety and idempotency are covered. The description adds 'Auto-paginated' and the dependency-check use case, but does not disclose return shape, permission implications, or other behavioral details beyond that.

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?

Three short, front-loaded sentences with no filler. Purpose, usage timing, and pagination behavior are each stated compactly and nothing is repeated unnecessarily.

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 5-parameter read-only list tool with full schema descriptions and annotations, the description covers purpose, when to call it, and pagination. It stops short of describing the returned relation structure, but the absence of an output schema makes that a minor gap rather than a critical omission.

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%, and the schema fully documents the limit, scope, entry_ids, link_direction and include_permissions_info parameters. The description's first sentence loosely echoes the link_direction concept but adds no syntax, defaults, or meaning beyond what the schema already provides.

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: listing what DataLens entries use or are used by, with concrete examples (chart's dataset, dataset's connection). This dependency-relation purpose is clearly distinct from sibling list tools like datalens_entries_list or datalens_entries_revisions_list, even without naming them.

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?

Explicitly says to use it before changing or deleting an entry to see what depends on it, which gives clear context for when to invoke it. It does not name alternative tools or when-not to use it, so it falls short of full 5-level routing guidance.

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