norns_get_param

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

With no annotations, the description carries the full behavioral burden, and it only hints at the return payload. It says nothing about whether the operation is read-only, what happens when param_id does not exist, or whether the display string can differ from the raw value (e.g., scaling, formatting).

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 single fragment is front-loaded and free of padding, so nothing is wasted, but it is under-specified rather than concise. A few more words about the identifier format would pay for themselves.

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?

This is a simple one-parameter getter and an output schema exists, so return values need not be explained. Still, the unresolved param_id format and the lack of any error or empty-result behavior leave meaningful gaps for an agent trying to call it correctly.

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 schema gives only the name 'param_id' with a string type. The description's phrase 'One param's' implies param_id identifies a param but adds no format guidance—whether it is a name, index, or numeric id—which is the single most important ambiguity for this tool.

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 what the tool returns ('raw value and display string') for a single param, which implies a getter, but it omits an explicit verb and never distinguishes itself from norns_params (list all params) or norns_set_param. The agent must infer the read-vs-list distinction from the name alone.

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 mention of when to prefer norns_params instead, and no note on prerequisites such as a script needing to be loaded. Usage must be inferred entirely from the tool name.

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