Api assets export csv retrieve

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing about the CSV output itself — column set, row scope, whether it streams a file, whether it honors active filters — and its 'viewed or edited' wording sits awkwardly with a read-only export endpoint.

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?

It is a single short sentence, so it is not bloated, but the one sentence it contains is boilerplate that does not earn its place. Brevity here comes from under-specification rather than efficiency.

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?

There is no output schema and no parameters, so the description is the only place an agent could learn that this returns CSV content rather than a JSON asset list. That crucial detail is missing, leaving the tool indistinguishable in practice from the plain assets list endpoint.

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?

The input schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. It is worth noting, though, that the description gives no hint about what gets exported, which is the only 'parameter-like' semantics this tool has.

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 is generic Django-REST-Framework boilerplate ('allows assets to be viewed or edited') and never states that this tool exports assets as a CSV file, which is what the name and route indicate. It restates a resource without a specific verb and gives no way to distinguish it from sibling endpoints such as assets_list or assets_export_xlsx_retrieve.

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 guidance is given at all — nothing says to call this for a CSV dump versus assets_list for JSON or assets_export_xlsx_retrieve for a spreadsheet. The 'viewed or edited' phrasing even suggests generic CRUD usage rather than a one-shot export.

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