uad_get_plugin_params

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals a key constraint: the tool only works on loaded plugins and empty slots are invalid. It also clarifies that this is a read/list operation, implying no mutation, and describes the kind of output to expect.

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 concise sentences, front-loaded with the main purpose and followed by usage guidance. There is no fluff or repetition of schema details.

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 the purpose and usage are clear and an output schema exists, the tool has three parameters (all undocumented) and no annotations. The description does not sufficiently explain how to identify the target plugin, leaving a critical gap for successful invocation.

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?

The schema description coverage is 0%, so the description must compensate, but it provides no meaning for the parameters slot, device, or target. The required 'target' parameter is not explained at all, making it impossible for an agent to know what value to provide.

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 action ('List') and the resource ('a loaded plugin's parameters'), and specifies what is returned (names, normalized 0-1 values, display text). This distinguishes it from sibling tools like uad_set_plugin_params or uad_get_status.

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?

Explicitly provides 'Use when' scenarios and a 'Not for' exclusion with a rationale (parameter nodes only exist once a plugin is loaded). This gives clear context for when to choose this tool over alternatives.

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