RALE Command (full; read + write)

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

The description adds that every call surfaces a toast in Dev Studio, complementing the annotations (destructiveHint=true). It reinforces the destructive nature with examples.

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 short sentences, each adding critical information: the tool's purpose, a key alternative, and a side effect. No wasted words.

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?

While it covers the main use case and destructive intent, it lacks details on return values or error handling. For a tool with no output schema and destructive potential, more context is needed.

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 schema description coverage at 67%, the description adds little beyond restating command purpose. It does not elaborate on 'args' or 'device' parameters beyond what the schema provides.

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 it runs any built-in RALE command, including destructive ones, and points to list_rale_builtins for the catalog, distinguishing it from siblings.

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?

It explicitly advises using list_rale_builtins for the catalog and hints at destructive use, but does not fully specify when to use this tool over other sibling tools like get_action_schema.

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