List directory

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Directory reads' aligns with those. It adds valuable behavior beyond annotations: users_groups responses are session-cached for ~5 minutes and refresh=true forces a reload. No contradiction with annotations.

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?

Two short sentences with no filler. The purpose is front-loaded, and the cache/refresh behavior is stated in a compact, directly actionable way.

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 the output schema exists and annotations cover the read-only safety profile, the description is mostly complete: it names the main sources and explains the important cache/refresh behavior. The main gaps are the mismatch between 'additional operators' and the enumerated additional_users/additional_rights, and the lack of any distinction from the sibling list_users_groups.

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 50%; source is described as 'Directory Get source.' and refresh has no schema description. The description compensates partially by explaining that users_groups is cached and refresh=true forces reload, which gives the refresh parameter real meaning. However, it does not clarify the enum values such as additional_users and additional_rights, only vaguely referring to 'additional operators.'

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 states a specific action ('Directory reads') and lists the resources covered: users/groups tree, users, groups, computers, and additional operators. It is clear enough, but it does not explicitly differentiate from the sibling list_users_groups and uses 'additional operators' rather than the exact enum values additional_users/additional_rights.

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 explicit guidance on when to use this tool versus alternatives such as list_users_groups. The caching note ('users_groups is session-cached (~5 min); pass refresh=true to force reload') helps with the refresh parameter, but it does not explain when this tool is the right directory read vs another sibling tool.

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