get_global_policies

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

No annotations are provided, so the description carries the burden. The verb 'Get' implies a read-only operation, which is the essential behavioral fact. It does not disclose any further behavior, such as authorization expectations or what happens when no policies exist, but for a parameterless getter this is a minimally acceptable but not rich disclosure.

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 a single well-structured sentence that leads with the action and resource, then lists illustrative policy categories without unnecessary detail. It earns its place and avoids over-explanation.

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?

This is a low-complexity, no-parameter getter with an output schema available, so the description is largely enough to invoke the tool correctly. It would be slightly stronger with a note distinguishing it from the similarly named getters, but nothing critical is missing.

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 input parameters, so the schema already fully defines the empty input. The description adds no parameter-level meaning, but that is not needed here; the baseline for a 0-parameter tool is therefore an adequate score.

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 clearly states the action ('Get') and the resource ('global VDI policies') while giving concrete policy categories (USB redirection, multimedia redirection, clipboard settings). It does not explicitly differentiate itself from siblings like 'get_settings' or 'get_environment_properties', so it misses the top score.

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?

The description only says what the tool returns and provides no when-to-use guidance, prerequisites, or alternatives. There is no clue about when an agent should choose this over the similar get_settings or get_environment_properties, making this dimension weak.

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