list_domain_controllers

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether it's destructive, what format the output takes, or any rate limiting considerations. The single sentence provides zero behavioral context beyond the basic action implied by 'List'.

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 maximally concise - a single three-word phrase that communicates the core action. There's no wasted language or unnecessary elaboration. While this conciseness comes at the cost of completeness, as a standalone measure of brevity and structure, it's perfectly executed.

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 tool with 1 undocumented required parameter, no annotations, no output schema, and operating in a complex Active Directory/security context with many similar sibling tools, this description is completely inadequate. It provides no information about what the tool actually does beyond the name, no parameter guidance, no behavioral context, and no differentiation from alternatives. The agent would struggle to use this tool correctly.

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?

The schema has 1 parameter with 0% description coverage, meaning the 'domain' parameter is completely undocumented in the schema. The description provides no information about this parameter - not what it represents, what format it expects, whether it's a domain name or identifier, or what happens if an invalid domain is provided. For a tool with a required parameter and zero schema documentation, this is critically inadequate.

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 'List domain controller(s)' is a tautology that essentially restates the tool name with minimal elaboration. It specifies the verb 'List' and resource 'domain controller(s)', but lacks any detail about scope, format, or what constitutes a domain controller in this context. While it distinguishes from some siblings by focusing on domain controllers, it doesn't differentiate from tools like 'list_domain_computers' or 'list_certificate_authority_servers' that might also list specific server types.

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 provides absolutely no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context requirements, or any comparison with sibling tools like 'list_domains' or 'list_domain_trusts'. The agent receives no help in determining when this specific listing tool is appropriate versus other domain-related listing tools.

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