ad_generate_domain_inventory

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

No annotations are provided, so the description carries the full behavioral burden, yet it only contributes the '[READ]' tag implying a non-mutating operation. It says nothing about cost/size of a full-domain inventory, required privileges for a complete enumeration, or whether correlation_id enables async tracking — all real concerns for a domain-wide sweep.

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 single sentence is front-loaded and wastes no words, but brevity here reads as under-specification rather than disciplined concision — the tag vocabulary ('Reports, Inventory & Automation') consumes part of the limited text without adding operational meaning.

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?

An output schema exists, so return structure needn't be re-explained, but for a domain-wide inventory operation with zero annotation coverage and zero parameter documentation, the description is too thin. It omits what the inventory covers and any execution caveats an agent would need before invoking a potentially expensive directory scan.

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% for both parameters. The description does not state which output_format values are accepted (the schema gives only a free-form string defaulting to 'json', with no enum) nor what correlation_id is for. The parameter names are semi-self-describing, but valid value ranges are left entirely to guesswork.

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 verb+resource ('generate complete inventory of the domain') is identifiable, but 'inventory' is materially vague — it doesn't say what is inventoried (users, computers, OUs, GPOs, all of the above) or how it differs from near-identical siblings like ad_generate_domain_health_report or ad_generate_security_audit_report. An agent can guess it is a bulk read but cannot tell what it returns without opening the tool.

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 guidance on when to choose this over the many ad_generate_*_report siblings, no prerequisites, and no exclusions. The only navigational cue is the bracketed '[Reports, Inventory & Automation]' category tag, which is not enough to route between competing report generators.

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