openclaw_config_get

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

Discloses that the tool is read-only and that the gateway always returns the full config, with path applied client-side. No annotations exist, so the description carries the full burden; it covers key behavioral traits but omits error scenarios or auth requirements.

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?

Two concise sentences, front-loaded with purpose, followed by essential behavioral detail. No wasted words; every sentence adds value.

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 no output schema, the description adequately states it returns the full config. The two parameters are fully covered by schema and description. For a simple read tool, all necessary information is present.

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?

With 100% schema coverage, the description adds the crucial insight that path does not filter server-side, which is not evident from the schema alone. Instance parameter is well-documented in schema; description does not add extra but does not detract.

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 the tool reads the gateway's current configuration and explicitly marks it as read-only. It distinguishes from sibling write tools like openclaw_config_set/openclaw_config_patch by verb and usage of 'read'.

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?

Explains that the path parameter is applied client-side and does not reduce wire traffic, which guides proper usage. Does not explicitly compare to other read operations, but given no sibling read config tools, the guidance is sufficient.

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