Update DataLens collection

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context with the partial-update semantics (omitted fields are preserved), but says nothing about required permissions or failure modes for a non-existent collection.

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 the mutation front-loaded ('Change a collection's title or description') and the semantics clause appended. No wasted words, though it is terse enough that nothing extra is offered.

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 three-parameter update with full schema coverage and annotations carrying idempotency and safety, the description is adequate but thin: it omits permission requirements and any note on what identifies an invalid collection_id. No output schema exists, so return behavior need not be described.

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 the schema already documents title, description and collection_id. The description adds the partial-update meaning for the optional fields but no extra syntax, format or constraint detail 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 names a specific verb (change) and resource (a collection) and lists the two mutable fields, title and description. It is clearly distinct from siblings like datalens_collections_move or datalens_collections_delete, though it does not explicitly contrast itself with any of 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?

The phrase 'what is not given stays as it is' effectively tells the agent this is a partial update, which is useful usage context. However, there is no explicit when-to-use guidance, no prerequisites (e.g. ownership/permissions), and no named alternative for a full replacement.

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