Run Command

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

Annotations already declare readOnlyHint=false, openWorldHint=true and non-idempotent, which tells the agent this mutates remote state. The description adds nothing beyond that: no mention of fan-out blast radius, no warning that cmd is arbitrary shell, no reference to preview/scope verification, and no timeout behavior — all of which are the key risks for this tool.

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 with the name restated first, so it is front-loaded and wastes few words. However, the only content sentence ("Bulk inventory operations against YAML host groups") is vague enough that brevity tips into under-specification.

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 16-parameter tool that executes arbitrary shell commands across many hosts, the description says nothing about the single-host vs group targeting model, the preview safety path, or the risk of unintended fan-out. An output schema and rich parameter docs exist, but they don't substitute for a warning about what this tool actually does at scale.

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 100%, and the schema itself is unusually rich (host vs group precedence, preview semantics, timeout, parallel/max_threads are all documented inline). The description adds no parameter meaning at all, so the baseline 3 for high coverage applies.

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 verb+resource is present ("Run command"), and "against YAML host groups" hints at the fan-out scope that distinguishes it from tm_remote_run_command. But "Bulk inventory operations" is vague and doesn't say the tool executes a shell command over SSH across a group of hosts, so the agent must infer the actual behavior.

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?

Nothing says when to use this instead of tm_remote_run_command or the other tm_inventory_* siblings. The word "bulk" implies the fan-out case, but there are no explicit conditions, prerequisites, or exclusions given.

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