get_current_time

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

Without annotations, the description carries the full burden and does disclose the return value (currentTime in microseconds) and the broadcast behavior that no responses are returned when motor='all'. However, it does not explicitly state that the operation is read-only or describe side effects, which would have strengthened transparency.

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 reasonably concise and front-loads the main purpose, then lists returns and parameter options. The bracketed firmware command group adds minor clutter but does not significantly harm readability.

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?

For a simple one-parameter read tool, the description covers the input format, return value, and the key broadcast caveat. It lacks an explicit statement that the tool is non-destructive, but the overall context is sufficient for correct invocation.

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 provides no parameter descriptions, but the description fully explains the motor parameter: alias number, 16-hex-digit ID, or 'all' for broadcast. It also gives concrete examples and notes the important no-response consequence of broadcasting, which is exactly the kind of semantic detail an agent needs.

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 clearly states the tool gets the current absolute time, with a specific resource and verb. It is distinct from siblings like reset_time and time_sync, though it does not explicitly call out those alternatives, so it falls short of a full 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?

There is no guidance on when to use this tool versus siblings such as time_sync or get_motor_status. The description provides no conditions, exclusions, or alternative tool recommendations, leaving the agent to infer appropriate usage.

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