Api security exceptions export csv retrieve

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

The description claims the endpoint allows exceptions to be "viewed or edited," while annotations declare readOnlyHint=true and destructiveHint=false. For a CSV export endpoint this is a direct contradiction and would suggest write capability that does not exist. It also adds nothing about the export behavior itself (that a CSV payload is produced).

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 with no padding, so it is size-appropriate, but the sentence itself is generic template text that conveys little. Brevity comes from under-specification rather than from efficient information density.

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 zero-parameter export tool with no output schema, the description should say that it returns a CSV file of security exceptions (and whether any filters or scoping apply). Neither is covered, and the only content present is misleading rather than merely absent.

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 (and the empty properties object) fully specifies the call shape and the description has nothing extra to document. Baseline 4 applies for a parameterless 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 description names the resource ("security exceptions") but never states the actual operation the tool performs: exporting a CSV file, as the name and title make explicit. Worse, it says the endpoint is for viewing or editing, which is neither the export verb nor distinguishable from siblings such as security_exceptions_list, _retrieve, or _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?

There is no when-to-use information at all, and no mention of the obvious alternative (ciso_assistant_api_security_exceptions_export_xlsx_retrieve) or of when the CSV form is preferable. The agent is left to infer everything from the tool name alone.

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