inspect_ros_clock

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so restating 'read-only' adds little. The genuinely additive content is the scope disclosure that sim time is not compared to UTC, which tells the agent what this tool will not report; however, nothing is said about how observation is performed or what the observation window affects.

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 compact sentences with the core observation capability front-loaded and the scope caveat last. Minor waste in 'read-only' duplicating the readOnlyHint annotation, but nothing else is padding.

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, and the safety profile is covered by annotations. The remaining gap is the sole parameter, which is left undefined for a tool whose whole usefulness depends on watching the clock over an interval.

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% and there is one parameter, duration_s (default 2, range 0.1-30), whose meaning is entirely undocumented in both schema and description. The most plausible reading is an observation window, but the agent must guess that, and guessing wrong changes whether a pause or backwards jump is even detected.

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 resource (/clock) and specific operations (observe progression/pause/backwards, query per-node use_sim_time), which is far more than the tool name alone conveys. It is reasonably distinguishable from siblings like analyze_ros_timestamps or compare_ros_topics, though it never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: an agent can infer this is the ROS simulation-clock diagnostic tool, and the closing scope note ('simulation time is never compared to UTC') hints at an exclusion. But no sibling is named and no condition is given for choosing this over analyze_ros_timestamps or get_timestamp_capabilities.

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