get_rootdse_info

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

With no annotations present, the description carries the load and does reasonably well: it declares there is no input, that a fixed attribute allow-list is read (a real behavioral constraint that prevents the agent from requesting arbitrary attributes), and lists what comes back. It omits authentication/bind requirements and any failure behavior, which is the remaining gap.

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?

Well front-loaded: purpose first, then return contents, then the no-input constraint, then a concrete example call and a one-line use case. No redundant restatement of the name and nothing wasted.

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?

With no output schema and no annotations, the description does the necessary work by enumerating the returned fields (naming contexts, DC host name, functional levels, LDAP versions, SASL mechanisms, time, sync/GC state). What's missing is bind/anonymous-auth expectations and error conditions, minor for a read-only diagnostic call.

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 tool takes zero parameters and the description confirms this explicitly ("Takes no input"), plus notes the fixed allow-list that shapes the call. Baseline for a zero-parameter tool is 4, and nothing here detracts from that.

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 opens with a specific verb+resource (rootDSE information from the domain controller) and enumerates the returned attributes, so the agent knows exactly what it gets. It does not explicitly distinguish itself from the nearby get_domain_info, get_schema_info, or test_connection siblings, which is the only thing keeping it from a 5.

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?

One use case is stated ("Useful to confirm which DC answered and its functional level"), which is genuinely helpful context. However there is no indication of when NOT to use it, nor any pointer to the alternatives (get_domain_info, test_connection, health) that an agent could easily confuse it with, so routing remains partly inferential.

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