plugin_get_param

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

The description provides no behavioral details beyond the basic action. No annotations exist to compensate. It fails to disclose whether the operation is read-only, what happens if the parameter is invalid, or the return type.

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 a single sentence but lacks structure and important details. While concise, it sacrifices informativeness for brevity, which is not ideal for a tool with four parameters.

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?

With no output schema and four parameters, the description is severely incomplete. It does not explain the tool's context (e.g., plugin indexing, parameter numbering) or the expected return value, making it insufficient for reliable agent usage.

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 should explain parameter meanings. It does not mention 'index', 'param', 'slot', or 'location', leaving the agent without context for how to use them.

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 'Get value of a single parameter' clearly states the action (get) and resource (parameter value). It implicitly distinguishes from sibling tools like 'plugin_set_param' (write) and 'plugin_params' (multiple values), but lacks explicit differentiation or context about which plugin.

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?

No guidance on when to use this tool versus alternatives (e.g., 'plugin_params' for all parameters, 'plugin_find_param' for discovery). No prerequisites or context (e.g., plugin must be valid or selected).

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