ipc_execute_command

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

Annotations provide readOnlyHint=false and destructiveHint=false, and the description adds that it invokes Rust backend functions, implying both read and write capabilities. It also notes the Tauri-specific context and the driver_session requirement, adding behavioral context beyond annotations.

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 brief at three sentences, each serving a distinct purpose: stating the function, mentioning the prerequisite, and clarifying the framework scope. No unnecessary words, and key information is front-loaded.

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 tool with 3 parameters and no output schema, the description covers the essential context: what it does, prerequisite, framework specificity, and usage boundaries. It is complete enough for an AI agent to decide when to use this tool.

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 coverage is only 33% (only appIdentifier has a description in schema). The description does not elaborate on the 'command' or 'args' parameters, missing the opportunity to explain their structure or expected format, which is needed given low schema coverage.

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 executes Tauri IPC commands to invoke Rust backend functions, using a specific verb and resource. It distinguishes itself from sibling tools for browser APIs and Electron IPC, making its purpose 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?

The description explicitly states the prerequisite ('Requires active driver_session') and provides clear guidance on when not to use it ('For Electron IPC or browser APIs, use appropriate tools for those frameworks'), offering explicit alternatives.

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