Api applied controls sunburst data retrieve

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

The description claims the endpoint allows applied controls to be "edited", while the annotations declare readOnlyHint=true and destructiveHint=false on a `_retrieve`-suffixed endpoint. That is a direct contradiction that could lead an agent to attempt a write. The description also adds nothing about what sunburst data actually contains (node hierarchy, grouping dimensions, aggregation).

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 with no padding, so structurally fine. But the sentence is pure boilerplate that carries no information, so brevity buys nothing here.

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 and no parameters, the description is the only place an agent could learn that this returns sunburst (hierarchical) chart data for applied controls – and it says nothing about that. For a zero-annotation-detail chart endpoint, this leaves the caller unable to predict the response shape.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. It neither helps nor hurts on this dimension.

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 says only that the endpoint "allows applied controls to be viewed or edited" – generic Django-REST boilerplate that never mentions sunburst data or the hierarchical chart payload the tool actually returns. Against dozens of sibling applied-controls endpoints (list, retrieve, analytics, per_status, priority_chart_data), it gives an agent no way to distinguish this tool's purpose.

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 statement of when to use this endpoint versus the many alternatives (e.g. applied_controls_list, applied_controls_analytics_retrieve, applied_controls_priority_chart_data_retrieve, or the findings/policies sunburst equivalents). The only implied guidance is the word "viewed", which is far too weak to route an agent.

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