dcs_assets

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

Annotations already declare readOnlyHint=true, so the "[READ]" tag adds nothing new. "Bounded page" is the only behavioral signal, hinting at pagination but not stating default page size, whether more pages exist, or how to detect truncation.

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 front-loaded sentence with no filler and the read-only marker placed first. It is efficient, though efficiency here partly reflects under-specification rather than disciplined editing.

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 four-parameter list endpoint with no output schema and an undocumented required sort argument, the description leaves too much unknown. An agent can guess it paginates, but not how to sort, how large pages are, or what an asset record contains.

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 0% across four parameters, including a required "sort" whose accepted values are completely unknown. The phrase "bounded page" loosely implies limit/offset but provides no format, range, or sorting syntax, so the description fails to compensate for the coverage gap.

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 gives a specific verb and resource ("List ... assets") and adds the pagination qualifier "bounded page". However, it never distinguishes this collection endpoint from siblings such as dcs_asset (single asset detail) or dcs_asset_stats, so an agent must infer the difference from names alone.

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?

There is no guidance on when to use this tool versus dcs_asset, dcs_asset_stats, or dcs_asset_errors. No prerequisites, no exclusions, and no mention of what happens if the result set exceeds the page size.

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