Api policies export csv retrieve

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

Annotations declare readOnlyHint=true and destructiveHint=false, yet the description claims the endpoint permits records to be 'edited'. That is a direct conflict with the declared safety profile, and no export-specific behavior (output format, file download, payload shape) is disclosed.

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, front-loaded sentence, so it is structurally fine. But its content is boilerplate about the wrong entity, so brevity comes at the cost of being uninformative rather than efficient.

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 an export tool with no output schema, the description should say what is produced (a CSV file of policies), what it contains, and whether it reflects all policies or a filtered set. None of that is present, and the stated subject matter is incorrect.

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 schema leaves nothing to explain; the description is not required to add parameter detail. It neither helps nor harms here, which is the baseline for a no-parameter tool.

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 tool name and title indicate a CSV export of policies, but the description instead says it 'allows applied controls to be viewed or edited' — the wrong resource entirely and no mention of export or CSV. An agent reading only the description could not distinguish this from an applied-controls CRUD endpoint.

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, and the obvious alternative (ciso_assistant_api_policies_export_xlsx_retrieve, or policies_list) is never referenced. The description's 'viewed or edited' phrasing actively suggests a generic retrieve/update endpoint rather than an export.

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