Api compliance assessments export retrieve

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

Annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, yet the description says the endpoint allows assessments 'to be viewed or edited' — implying a write capability the annotations explicitly deny. The description also withholds what the export actually produces (serialized file? JSON export payload?), which is the one behavioral fact an agent needs here.

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 not verbose, but the content is generic boilerplate rather than a front-loaded statement of what the tool does. Brevity here reflects low information, not 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, an undocumented 0%-coverage id parameter, and no explanation of export behavior or the returned payload, the definition leaves too much open for a tool that presumably serializes a compliance assessment. The annotations cover the safety profile but nothing else.

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 single required parameter 'id' has 0% schema description coverage, so the description must carry the burden and says nothing about it — not whether it is a UUID, a ref_id, or a numeric key. The bare parameter name is the only clue available to the caller.

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 restates the tool name at a generic level: 'allows compliance assessments to be viewed or edited.' It never mentions the 'export' function that distinguishes this endpoint, nor does it separate it from siblings such as compliance_assessments_retrieve, _object_retrieve, _list, or _cascade_info_retrieve. An agent cannot tell what is actually returned here beyond 'some compliance assessment data.'

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 guidance and no mention of alternatives, despite a dense cluster of sibling compliance-assessment read endpoints. The boilerplate 'viewed or edited' gives no condition under which an agent should pick this over the plain retrieve or object_retrieve variants.

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