bridge_send_command

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails it. It says nothing about the token parameter being an auth credential, nothing about what allow_exec unlocks (an arbitrary-execution switch is the single most important thing to disclose), nothing about blocking behavior, timeouts, or what a failed send returns. Only the implicit 'running game' prerequisite is conveyed.

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?

The single sentence is front-loaded and free of padding, so it is concise. However, the brevity stems from under-specification rather than discipline; there is room for two or three sentences of genuinely load-bearing context at no cost to readability.

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 six-parameter tool with no annotations and no output schema, the definition is far too thin. An agent cannot safely determine authentication requirements, the args_json encoding, the risk profile of allow_exec, or what a successful versus failed send looks like from this description alone.

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 six parameters, and the description compensates for none of them. It references only 'command' in passing and says nothing about host/port, the token's authentication role, the args_json string format (it is a JSON string, not a structured object), or what allow_exec toggles. This is exactly the case where the description must carry parameter meaning and does not.

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 names a specific verb (send) and resource (a command) and identifies the target: a running game reached through the live bridge .ts4script. The sibling tools are all package/tuning/script build utilities, so this is clearly distinguishable. It stops short of stating what a 'command' is or what the bridge protocol covers, but the core action is unambiguous.

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?

There is no when-to-use guidance, no stated prerequisite that the game must be running with the bridge script loaded, and no mention of alternatives or fallbacks. An agent must infer entirely on its own when this live-bridge path applies versus the offline package/tuning tools in the sibling set.

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