param_list

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

The description explains the effect of the 'evaluate' parameter (numerical values vs. expressions) and the return format (dictionary). Since no annotations are provided, the description carries the full burden and adequately discloses the tool's behavior, though it could mention that it is read-only.

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 concise with a front-loaded purpose sentence followed by clearly structured Args and Returns sections. No extraneous information.

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?

The description covers the return type (dictionary of parameters) and parameter effects. Given no output schema, this is sufficient for a list tool, though it could include an example or mention potential errors.

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 coverage is 0%, but the description fully compensates by explaining both parameters: 'model_name: Model name (default: current model)' and 'evaluate: If True, return numerical values; if False, return expressions'. This adds essential meaning beyond the schema's type and default.

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 clearly states 'List all parameters in a model,' providing a specific verb (list) and resource (parameters in a model). This distinguishes it from sibling tools like param_get (specific parameter) or param_set.

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., param_get for a single parameter). The description does not mention exclusions or context for usage.

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