command_execute

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

With no annotations, the description carries the full disclosure burden and does so well for the risk profile: it warns that commands may be non-idempotent, that an unknown outcome may mean the command already ran, and that automatic retry is forbidden. It omits other relevant traits such as required permissions and the fact that dry_run defaults to true, which materially changes whether anything actually executes.

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, front-loaded with the action and followed by the critical failure-mode caveat. No filler and nothing buried.

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-shape explanation isn't required, and the description correctly ties the "unknown outcome" language to the result. However, with 0% parameter coverage and no annotations, the omission of dry_run semantics and execution permissions leaves the definition materially incomplete for a mutating command tool.

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% across three parameters, so the description must compensate, yet it explains none of them. Only "on one device" implies the device parameter is singular rather than a list; command and especially dry_run (defaulting to true, i.e., no execution unless changed) are left entirely unexplained.

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?

States a specific verb and resource: "Execute a command on one device." The scope (single device) is clear and the sibling device_list is obviously a different operation, so an agent won't confuse them, though the description never explicitly contrasts 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 by the non-idempotency warning, but there is no explicit when-to-use/when-not framing or named alternative beyond the unrelated device_list. The retry warning is useful context but is behavioral guidance rather than selection guidance.

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