openclaw_call

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

Emphasizes the destructive nature and user validation requirement. Lists mutating method patterns to watch for. Despite no annotations, the description fully discloses risks and constraints.

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?

Front-loaded warning, two sentences of purpose, and clear parameter guidance. No redundant content; every word earns its place.

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 generic nature and large sibling set, the description perfectly covers when to use, what to expect, and how to invoke safely. Lacks output schema but tool returns raw RPC response, which is adequately implied.

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?

Adds value beyond the 100% coverage schema: explains the method naming convention, warns that params must be an object, and clarifies instance fallback behavior. No gaps.

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?

Clearly states 'call ANY JSON-RPC method on the gateway with arbitrary params' and distinguishes from typed alternatives. The phrase 'DESTRUCTIVE ESCAPE HATCH' immediately signals its role.

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?

Explicitly says 'Use this to operate on endpoints that don't yet have a typed wrapper' and warns to prefer typed tools for read-only inspection. Provides concrete examples of when not to use.

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