Api entities export csv retrieve

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

Annotations declare readOnlyHint=true, yet the description says entities can be 'edited' via this endpoint, implying a write capability that the annotations deny. It also omits the one behavioral fact that matters here - that the response is a CSV file export - so it adds nothing usable and contradicts the structured safety profile.

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, but it is boilerplate that conveys no actionable information and is not front-loaded with the export behavior. Brevity here reflects 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?

With no output schema and no parameters, the description is the only place to explain that the call returns a CSV of entities (and any scope/filter behavior). It omits all of that, so an agent cannot know what it will receive.

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 tool takes zero parameters, so the baseline is 4; there is no parameter semantics for the description to explain and nothing is missing on that axis.

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 DRF boilerplate: 'allows entities to be viewed or edited' names the resource but never says this tool exports entities as a CSV file, which is the only thing distinguishing it from entities_list or entities_export_xlsx_retrieve. It restates a vague CRUD notion rather than stating a specific verb+output.

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 when-to-use or when-not-to-use guidance and no mention of the alternative export tools in the sibling list (entities_export_xlsx_retrieve, entities_list). An agent has no textual basis for choosing this over another entity read tool.

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