policy_policies__get_policy

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on permissions needed, error behavior for a missing UUID, or what 'details' resolves to.

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 short and front-loaded, but the content is largely redundant: the REST path duplicates the title annotation and 'Get policy details' repeats the first clause. Brevity here reflects minimal content rather than disciplined editing.

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 a simple read-only getter with full annotation and schema coverage and no output schema, this is barely adequate. An agent still lacks any sense of the response shape or of what distinguishes policy details from the assignment and list endpoints.

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?

Schema description coverage is 100%, including documentation for the local 'fields' projection parameter and the policyUuid reference, so the baseline applies. The description contributes no additional meaning about either parameter.

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 'Get policy ... Get policy details', which confirms this retrieves a single policy resource, but it essentially restates the tool name and title annotation. It gives no indication of what a policy contains or how it differs from the sibling policy_policies__list_policies.

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 at all. In a family containing list_policies and policy_assignments__get_policy_assignment, the description never tells the agent to call this when it already has a policyUuid versus listing policies to discover them.

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