dpar_get

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

With no annotations, the description carries the behavioral burden. It discloses the core read operation and minvalmax option support, but it does not describe return type, error behavior, or what Min/Max/Opt Min/Opt Max actually do beyond relying on mpar_get.

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?

Two short sentences with the core purpose front-loaded and no unnecessary detail. Every word earns its place.

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 simple two-parameter getter, the description is close to adequate, but it assumes knowledge of mpar_get for minvalmax behavior and, with no output schema, does not state the returned value shape or error behavior.

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?

param_path already has a schema example, and minvalmax already has an enum. The description adds only 'same minvalmax options as mpar_get', which is a cross-reference rather than a full explanation of the parameter semantics.

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?

States a specific verb and resource: 'Get a DUT parameter value'. It is clearly distinct from dpar_set and dpar_exists, and referencing mpar_get hints at the DUT-vs-model parameter distinction, though it does not explicitly say when to use this over mpar_get.

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 explicit guidance on when to choose dpar_get versus alternatives like dvar_get, dpar_set, or mpar_get. The mpar_get reference only explains minvalmax option compatibility, not tool selection.

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