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

Annotations already establish readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: 'Only items you can view are listed' (permission-scoped results), that version listings are not paged while root/folder listings are, and how next_offset signals more results. It does not contradict the annotations and adds real behavior, but does not describe rate limits or auth requirements.

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?

One dense paragraph, but it is front-loaded and grouped logically: mode selection first, then pagination, then the search alternative. Every clause carries information, though the asset-item field list could be trimmed against the schema.

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?

With no output schema, the description correctly compensates by describing the returned item fields (asset_id, version_id, version_count, media fields, url, version_url) and the pagination envelope. For a five-param, zero-required tool its guidance is complete.

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 all five parameters, making 3 the baseline. The description reinforces the meaning of the three identifier modes and the limit/offset semantics, but mostly restates what the schema provides rather than adding syntax or edge-case detail.

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 (Browse) over specific resources (folders and assets) and enumerates the three entry modes (no id, folder_id, asset_id), which cleanly separates it from siblings like versions_add or tags. An agent can tell exactly what it returns per mode without opening the schema.

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 distinguishes the modes and names the alternative: 'To find something by name without knowing its folder, use search.' It also warns 'Not with folder_id' for asset_id, giving both when-to-use and a constraint against misuse.

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