List Gpos

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

Annotations already cover the read-only safety profile, but the description adds real value: the LDAP path read (`groupPolicyContainer` under `CN=Policies,CN=System,<base>`), the meaning of `cn` (GUID) vs `displayName`, and the failure mode of returning an empty list when the container is unreadable. That is above-average disclosure for a simple read tool.

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?

Three short sentences, front-loaded with purpose then implementation detail, with no filler. Slightly more LDAP internals than strictly necessary given an output schema exists, but each sentence is informative.

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 shape needn't be explained, and the read-only nature is annotated. However, with two undocumented parameters at 0% schema coverage, the description leaves the agent guessing about `limit` behavior and domain scoping.

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%, so the description must carry the burden and it largely doesn't. The `<base>` reference hints that `domain` scopes which naming context is read, but `limit` (pagination/truncation semantics) is never mentioned and `domain`'s behavior when null is unstated.

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?

States a specific verb and resource ("List Group Policy Objects") with an audit framing, which is unambiguous. It does not explicitly distinguish itself from the sibling `get_gpo`, though the plural/list framing implies the difference.

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 use this versus `get_gpo` or any other GPO-adjacent sibling. The agent must infer from the tool name alone that this is the enumeration entry point.

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