Api policies export xlsx retrieve

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

The annotations declare readOnlyHint=true and destructiveHint=false, but the description says records can be 'edited,' which implies a write operation and directly contradicts the read-only annotation. It also fails to disclose the export behavior implied by the tool name.

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?

The description is only one sentence, but that sentence is wrong and does not front-load the actual export purpose. Brevity cannot compensate for misleading content.

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 an export tool with no parameters and no output schema, the description should at least identify that it exports policies to XLSX. Instead it describes an unrelated applied-controls endpoint, leaving the agent without the essential context needed to select or invoke the tool 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 has zero parameters, so there are no parameter semantics for the description to clarify. The baseline for a parameterless tool is 4, though the description adds no useful context.

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 the endpoint allows 'applied controls' to be viewed or edited, but the tool name and title identify a policies XLSX export operation. It names the wrong resource and the wrong action, giving an agent no reliable understanding of what the tool does.

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 guidance on when to use this export endpoint versus the many sibling policy tools, such as policies_list, policies_export_csv_retrieve, or other export tools. The only usage signal is misleading because it describes viewing/editing applied controls.

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