plugin_get_param

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'get' and does not state whether the operation is strictly read-only, what value representation is returned, or how invalid plugin/parameter indices behave. It is not misleading, but it leaves the actual behavior under-specified.

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 front-loaded sentence with no filler: 'Get value of a single parameter.' It is appropriately concise for a simple getter, though the brevity comes at the cost of substantive detail that is penalized in other dimensions.

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 tool with four parameters, no output schema, and no annotations, this description is far too thin. An agent would need to guess the meaning of slot, index, and location, as well as the return type and error behavior, to call it reliably. This is inadequate for safe 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 has 4 parameters with 0% description coverage, and the description adds little semantic meaning. 'Single parameter' loosely maps to the param argument, but index, slot, location, and the default slot=-1 are not explained. The description does not compensate for the schema's lack of parameter documentation.

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 clear verb ('Get') and resource ('value of a single parameter'), and the word 'single' hints at a contrast with the sibling plugin_params (plural/list). However, it never explicitly names the plugin context or differentiates from plugin_set_param, so differentiation is mostly implicit.

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 guidance on when to use this tool instead of plugin_params, plugin_set_param, or plugin_find_param. An agent gets no hints about prerequisites, validation via plugin_is_valid, or which location/slot combination is appropriate. This is effectively no usage guidance.

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