ad_get_time_sync_status

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

No annotations are provided, so the description carries the full burden. It only signals '[READ]' and the category; it never states what is actually compared (PDC emulator? w32time?), what credentials or permissions are needed, whether it touches remote hosts, or what failure looks like. For a diagnostics tool with zero annotation coverage this is a substantial 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?

Extremely short with the category tag front-loaded, which is efficient, but the brevity here is under-specification rather than concision — there is no room left for the scope or parameter meaning an agent needs.

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 values need not be explained, but with no annotations, zero schema description coverage on two parameters, and no statement of what the check covers, the definition is not sufficient to call the tool confidently in a domain-controller context.

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% — both 'server' and 'correlation_id' are bare nullable strings with no documentation, and the description mentions neither. It does not explain what omitting 'server' (default null) means, whether it falls back to a local/default domain controller, or what format the server identifier should take.

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 names a specific verb+resource pair ('Verificar sincronizacao de horario' = verify time synchronization) plus category tags ('Replication, Health & Diagnostics', '[READ]') that place it in the diagnostic family. An agent can tell it apart from mutating siblings like ad_sync_replication, though it does not say which scope (local DC vs. a named server) it checks.

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 ad_get_replication_status, ad_get_dc_services_status, or ad_get_directory_health, all of which live in the same health/diagnostics family. No prerequisites, no exclusions, no stated trigger conditions.

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