Get Policy Window

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds 'maintenance/exclusion window' context but does not disclose additional behavioral traits like authorization needs or rate limits. The description provides modest value beyond annotations.

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 concise sentence (10 words) that is front-loaded with the verb. While efficient, it could include more detail without becoming verbose. It meets conciseness but slightly lacks completeness.

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?

Given a simple retrieval tool with an output schema (handling return values) and annotations, the description covers the core purpose. However, it omits parameter details and usage guidance, leaving gaps for a complete understanding. It is minimally adequate.

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 0%, so the description must compensate. However, it only mentions 'by UUID' without clarifying which parameter (window_uuid) is the identifier, and does not explain the optional org_uuid parameter or its default null value. This fails to add meaningful semantics beyond the schema structure.

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 uses a specific verb 'Retrieve' and specifies the resource 'details for a specific maintenance/exclusion window' with a clear method 'by UUID'. It effectively distinguishes this tool from siblings like search_policy_windows (search vs. get) and mutating windows (create, update, delete).

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies usage when a UUID is known, but does not mention search_policy_windows for cases where the UUID is unknown, nor does it state prerequisites or context for invocation.

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