list_parameters

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

No annotations are provided, so the description carries the full burden. It states only 'List all named parameters' with no disclosure of ordering, scope, pagination, or whether the result is model-wide. Nothing behavioral is added beyond the name.

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?

A single short sentence that is front-loaded and contains no filler. It is appropriately sized, though it is too sparse to earn a 5.

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 no-param, no-annotation, no-output-schema tool in a family with get/set/update_parameter siblings, the definition is too thin. It should at least say whether it lists model or user parameters and how it differs from the singular getter, since annotations and output schema provide no compensating context.

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 tool has zero parameters, so the baseline is 4. There is nothing for the description to clarify beyond the absence of inputs, and it does not mislead about parameters.

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 (List) and resource (named parameters). It is distinguishable from siblings like get_parameter, set_parameter, and update_parameter, though it lacks a noun-precision detail about parameter type. Still clear enough for an agent to pick this over the singular accessors.

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?

The description gives no when-to-use context, no exclusions, and names no alternatives such as get_parameter. The sibling set includes get_parameter, set_parameter, and update_parameter, so explicit differentiation would be valuable but is absent.

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