steam_rpc

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only hints at confirmation for uncurated commands but does not disclose error handling, permission requirements, or whether the tool causes side effects. This is insufficient for a tool that sends commands.

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 description is very concise at two sentences, but excessive brevity sacrifices critical detail. It is front-loaded with the core purpose, but the second sentence about confirmation is ambiguous.

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?

Given the complexity (7 parameters, 0% schema coverage, no annotations, output schema present but undiscussed), the description is severely incomplete. It fails to explain parameter formats, response structure, or error cases, leaving the agent with no actionable guidance beyond the bare purpose.

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?

The description adds no meaning to the seven parameters. With 0% schema description coverage, the agent receives no explanations for 'target', 'command', 'login', 'params', 'http_port', 'name_type', or 'confirmation_token', leaving the agent to guess their 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 clearly states 'Execute a Steam devkit RPC command' and mentions confirmation for uncurated commands, giving a specific verb-resource combination. It distinguishes this tool from siblings like 'steam_services' or 'steam_logs_manifest' by focusing on RPC commands, though the term 'RPC command' is somewhat generic.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks explicit context or prerequisites, only mentioning that uncurated commands require confirmation, which is a safety note rather than usage direction.

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