Api policies get controls info retrieve

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

The description says applied controls can be "viewed or edited", but the annotations declare readOnlyHint=true and destructiveHint=false. This directly contradicts the structured safety metadata and leaves the actual read-only behavior unclear.

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 only one sentence, but it is boilerplate ("API endpoint that allows...") rather than front-loaded with useful purpose. Brevity here reflects under-specification, not efficient communication.

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 retrieve tool with no output schema, the description should at least identify what is returned. Instead it is vague, suggests editing despite read-only annotations, and gives an agent no basis to select it confidently.

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 has zero parameters, so there is nothing for the description to clarify beyond the schema. Baseline 4 applies, though the description does not compensate for its other gaps.

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 calls this an "API endpoint" and says it relates to "applied controls", but the tool name is about policies getting controls info. It does not specify what controls information is retrieved or how this differs from the many sibling retrieve endpoints, including ciso_assistant_api_applied_controls_get_controls_info_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 indication of when to use this tool versus alternatives. It does not mention prerequisites, filtering, or when the related applied_controls and policies retrieve tools would be more appropriate.

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