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

Annotations already declare this as destructive, non-read-only, non-idempotent, and closed-world. The description adds useful context about prerequisite discovery and default resolution for omitted IDs, but does not explain execution side effects, permissions, or error behavior.

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?

Three short sentences, front-loaded with the core action, then the prerequisite, then the default-resolution rule. Every sentence provides actionable information with no waste.

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?

This is a destructive meta-tool with six parameters, a nested `args` object, and no output schema. The description covers discovery and ID defaults but leaves the most important invocation parameter, `args`, unexplained, along with side effects and result behavior.

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 description coverage is 0%, so the description must carry parameter meaning. It partially covers `tool` and the default behavior for `workspace_id`, `device_id`, and `directory_id`, but says nothing about the critical nested `args` object or `request_id`.

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 states a specific action, executing a tool on a connected device, and routes discovery to the sibling `discover`. It is clear enough to distinguish this from discovery, though the repeated generic term 'tool' slightly weakens precision.

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 tells the agent to use `discover` first to find tool names, device IDs, and workspace IDs. It also explains fallback behavior when workspace_id, device_id, or directory_id are omitted, though it gives no when-not-to-use guidance.

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