cipp_get_tenant_drift

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

Description states 'report' which aligns with readOnlyHint=true and destructiveHint=false, but adds no additional behavioral context such as permissions, rate limits, or response details. Annotations already cover the non-destructive nature, so description adds minimal value here.

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?

Two sentences, front-loaded with the key action 'Report standards drift'. No filler or redundant information. Every word earns its place.

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?

Adequately explains the tool's purpose and usage of the only parameter. Lacks details about the output format (e.g., list of drift items), but given the tool's simplicity and absence of output schema, the description is reasonably complete. Could clarify what constitutes 'drift' more explicitly.

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% (single parameter tenantFilter has a description in schema). The description repeats the schema's guidance about omitting for all tenants, adding no new meaning beyond what the schema already provides.

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?

Description uses specific verb 'report' and resource 'standards drift' with clear reference to tenant's assigned Standards Template. Distinguishes from sibling tools like cipp_list_standards and cipp_run_standards_check by focusing on deviation detection.

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?

Provides explicit guidance on omitting the tenantFilter parameter to report drift across all tenants. However, does not directly contrast with siblings like cipp_run_standards_check or cipp_get_tenant_alignment, leaving some ambiguity about when to choose this tool over alternatives.

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