execute_action

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

Annotations already indicate destructiveHint=true and idempotentHint=false. The description adds context about the generic params object and the two-tool interface but does not elaborate on side effects, permissions, or rate limits. With annotations covering safety, a score of 3 is appropriate.

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 sentences, no waste. Front-loaded with the core action, followed by usage context. Every sentence 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?

The description covers the main purpose and usage pattern but omits what the tool returns (no output schema). Given destructiveHint=true, some guidance on side effects would be helpful. Still adequate for a generic tool in a two-tool setup.

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 100%, and the description conveys that params keys depend on actionId, adding dynamic context beyond the schema's 'action arguments object'. This helps an AI understand that params are action-specific.

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 'Execute a UniFi action by actionId using a generic params object', specifying the verb, resource, and mechanism. It distinguishes itself from siblings by mentioning the stable two-tool interface pattern (search_actions + execute_action).

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 indicates usefulness for agents preferring a two-tool interface, implying usage when an actionId is obtained from search_actions. However, it does not explicitly exclude alternatives like client_action or device_action, which could be more specific for certain use cases.

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