Raw CLI command

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it runs an arbitrary command, with no mention of side effects, destructive potential, permissions, rate limits, or return format. The 'escape hatch' wording hints at risk, but without explicit disclosure an agent cannot anticipate consequences.

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?

At roughly two sentences plus an example, it is appropriately sized and front-loaded with the high-level purpose. The doc URL and example earn their place. It could be more structured with explicit guidance on when to use it, but it is not padded.

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 raw escape-hatch tool with no annotations and no output schema, the description does not provide enough context: no return/error semantics, no side-effect warning, no guidance on auth or server target. The doc URL helps but shifts the burden to the agent to go read external docs.

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 50%, and the description adds meaningful context for the command parameter by providing an example array. It does not explain the player parameter beyond the schema, nor how server-scoped vs player-scoped commands interact. The example is helpful but does not fully compensate for the uncovered parameter 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?

The description states a specific verb ('run') and a specific resource: an arbitrary LMS CLI command. It is clearly an escape hatch, distinct from purpose-built tools, and provides a concrete example command and a documentation URL. The purpose is unambiguous and distinguishes it from siblings that would handle specific operations.

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?

The phrase 'Escape hatch' implies use when no dedicated tool covers the need, but there is no explicit when-not-to-use or named sibling alternative. The documentation URL grounds usage, and the example clarifies command structure, but the description relies on inference that dedicated tools should be preferred and does not mention edge cases like authentication or server selection.

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