aadc.audit_defaults

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

The description indicates a 'warn-only scan' implying non-destructive behavior, but with no annotations, more detail would be beneficial—e.g., what gets scanned, performance impact, or result handling.

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?

Single sentence with key information front-loaded. Very concise, though the term 'Standard 7' may be obscure.

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 describes the tool's scope and non-destructive nature, but lacks explanation of 'Standard 7' and expected output format, which could hinder effective use.

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%, so the baseline is 3. The description adds no additional meaning to the parameters 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?

The description clearly states a specific verb ('scan') and resource ('default-true on suspicious privacy keys'), and distinguishes from siblings by referencing 'Standard 7' and a heuristic warn-only approach.

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?

No guidance on when to use this tool versus sibling audits like aadc.audit_all or aadc.audit_permissions. The description lacks explicit context for usage or alternatives.

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