param_get

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

Without annotations, the description discloses key behaviors: it returns a parameter value and an optional description, and the 'evaluate' flag controls whether a numerical value or expression string is returned. It does not detail error handling or performance, but the core behavior is well explained.

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 structured with Args and Returns sections, front-loading the main purpose. Every sentence adds value, and there is no redundancy or fluff. It is appropriately sized for the tool's complexity.

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?

Given the simplicity of the tool (3 parameters, no output schema), the description covers the primary functionality: retrieving a parameter value with optional model name and evaluate flag. It mentions the return format (value and description or error), which is sufficient. However, it could elaborate on error message structure or data types.

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%, so the description carries the full burden. It explains all three parameters: 'name' (parameter name), 'model_name' (default current model), and 'evaluate' (controls return type). This adds meaningful semantic information beyond the schema, though examples or accepted values are missing.

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 'Get the value of a model parameter', which is a specific verb and resource. It distinguishes itself from sibling tools like param_list (lists all parameters) and param_set (sets a parameter) by focusing on retrieval of a single parameter.

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 implies usage for retrieving a parameter value but provides no explicit guidance on when to use this tool versus alternatives such as param_list or param_description. No exclusions or context are given.

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