Api policies priority chart data 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 records can be 'viewed or edited', implying a write capability the tool does not have. It also omits any hint of what the chart payload contains, leaving the behavior opaque.

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 that is concise but carries no useful content — brevity here is under-specification rather than efficiency, since the only sentence present is inaccurate.

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 sole source of information about what this chart-data endpoint returns, and it supplies none — it instead describes a different resource. An agent has no basis for calling it correctly.

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 4 applies. The description does not misuse the empty schema, though it also adds nothing.

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 the wrong resource entirely: it says the endpoint lets 'applied controls' be viewed or edited, while the tool is a policies priority chart data endpoint (the applied-controls equivalent exists as a separate sibling). Nothing indicates it returns chart/aggregation data for policies, so an agent cannot tell what this tool actually produces.

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 mention of the sibling ciso_assistant_api_policies_priority_retrieve or ciso_assistant_api_policies_sunburst_data_retrieve that an agent would otherwise confuse this with. The single boilerplate sentence gives no selection criteria.

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