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

Annotations already declare destructiveHint=true, and the description does not contradict that. It adds genuinely useful context beyond annotations: the target host and the service account the command runs under. It still omits the traits that matter most for arbitrary execution, such as irreversibility, timeouts, working directory and whether output is captured.

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?

Three short clauses with zero filler, and the operative information (verb, host, identity) is front-loaded. Nothing could be cut without losing content.

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 tool that executes arbitrary commands on a named production host, the definition is thin on execution environment, output behavior and failure modes. Host, identity and the admin requirement are covered, and destructiveHint carries the safety signal, but there is no output schema to fall back on for return values.

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 coverage is 100%, so both the command string and the optional admin token are already documented in the schema. The description adds no meaning beyond that, such as shell flavor, command length limits or how the token interacts with the bearer-token path. Baseline 3 applies when the schema carries the semantics.

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 (run a shell command) plus the exact host (ops-console-01) and execution identity (svc-ops). That distinguishes it from siblings like run_sql, read_file and fetch_url, which are scoped to a particular protocol or resource rather than arbitrary shell.

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?

'Admin only' is a permission precondition, not a when-to-use rule. The description never says when to reach for this over run_sql, read_file or fetch_url, even though those are clearly narrower, safer alternatives for the same host.

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