read_drive_position_status

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: it reuses an existing heartbeat connection while the drive is running, and it degrades gracefully by returning raw command-pulse feedback when no coordinate reference exists.

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 clauses, front-loaded with the purpose and followed by the operational caveat. Nothing is wasted, though the heartbeat phrase is terse enough to be slightly opaque without knowing the broader connection model.

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 needn't be spelled out, and annotations cover safety. Still, for a tool whose only two parameters are fully undocumented, the description should say how port/transport are resolved and when to prefer this over read_drive_runtime_status.

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% for both parameters, so the description carries the burden and adds nothing: neither 'port' nor 'transport' is mentioned, nor is the default-selection or serial-vs-TCP choice explained. The only hint is the implicit assumption of an open heartbeat link, which is not tied to the transport parameter.

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 gives a specific verb+resource: read-only position feedback plus the validity of the coordinate reference. That distinguishes it reasonably from read_drive_runtime_status and configure_drive_position_reference, though it never names those siblings explicitly, so the boundary is inferred rather than stated.

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 only implied. 'During operation it reuses the heartbeat connection' and 'raw pulse feedback is still readable when no reference is established' tell the agent the tool is safe to call at any time, including before referencing, but there is no explicit when-to-use/when-not statement or comparison against read_drive_runtime_status.

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