User Bus Call

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is largely covered structurally. The description adds little beyond that — it names the 'defaultuser session bus' scope but says nothing about mutation risk, required permissions, side effects, or response behavior for a tool that can invoke arbitrary dbus methods.

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?

A single efficient sentence with no filler, and the core action is front-loaded. It is concise to the point of under-specification, but it wastes no 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?

For a 7-parameter, no-output-schema tool that can invoke arbitrary dbus methods on a session bus, the description is far too thin. It omits parameter meaning, usage conditions, and any behavioral/return context, leaving substantial gaps unfilled by schema or annotations.

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 only 43% across 7 parameters, and the description contributes no parameter meaning at all. It never explains destination, path, interface, member, or arguments, leaving the required dbus-send addressing fields undocumented outside the schema while the coverage gap remains.

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 gives a specific verb ('Run') and resource ('typed dbus-send method call on the defaultuser session bus'), which is more than a tautology. However, it does not distinguish this tool from the adjacent sibling sailfish_device_user_session_command, leaving the agent to guess which session-level tool to use.

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?

There is no when-to-use guidance, no when-not-to-use, and no named alternative. The description merely states what the tool does, not the situation that should select it over sailfish_device_user_session_command or sailfish_device_command_start.

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