Api policies sunburst data retrieve

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, yet the description says the endpoint allows data to be 'edited' — a direct conflict. It also never explains what the sunburst payload is (hierarchy levels, aggregation) or how costly/open-world the call is, despite openWorldHint=true.

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?

One short sentence with no padding, which is structurally fine. But brevity is achieved by being wrong and uninformative rather than by front-loading the essential fact (that this returns sunburst chart data for policies).

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?

There is no output schema and minimal annotations, so the description must explain what a sunburst data payload is and when to request it. Instead it describes a different resource and a different (write) capability, leaving the agent with no usable information about the return value or purpose.

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; baseline for a parameterless tool applies. No credit or penalty here — the description's problems lie elsewhere.

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 a resource ('applied controls') that is not this tool's resource — the tool name says 'policies' and 'sunburst data'. It also never mentions sunburst/chart data, so an agent cannot tell what this produces or distinguish it from the many sibling retrieve endpoints.

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?

No indication of when to use this versus siblings such as applied_controls_sunburst_data_retrieve, findings_assessments_sunburst_data_retrieve, or the plain policies_retrieve/list. The only hint is generic 'viewed or edited', which is not a usage condition.

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