Api compliance assessments quality check retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the scope word "every", which signals no filtering, but says nothing about the response shape, size, or cost of a bulk quality-check read. With annotations carrying the behavioral burden, a 3 is the right level.

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?

A single short sentence with no filler, and the scope qualifier is front-loaded. It is efficient, though the terseness borders on under-specification for a domain term like "quality check".

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, the description carries the full burden of explaining what a "quality check" returns, and it does not — the agent gets no idea of the result's fields or structure. It also leaves the ambiguity with the duplicate _retrieve_2 sibling unresolved, which matters for tool selection.

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 and the schema is fully described, so there are no parameter semantics for the description to compensate for. The description's "every" is consistent with the parameterless schema. Baseline 4 applies 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?

It states a verb ("Returns") and a resource ("the quality check of every compliance assessment"), but "quality check" is never defined, so the agent cannot tell what the result actually represents. It also fails to distinguish this tool from the near-identical sibling ciso_assistant_api_compliance_assessments_quality_check_retrieve_2, which is indistinguishable from the description alone.

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, no statement of prerequisites, and no mention of alternatives — including the direct duplicate sibling ending in _retrieve_2. "Every compliance assessment" implies an unfiltered bulk read, but that is inferred from the empty schema, not stated as a usage rule.

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