Create Parameter

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

Annotations already indicate this is a non-read-only, non-idempotent, non-destructive operation, and the description does not add behavior beyond that. It does not state what happens on duplicate names, whether existing values are overwritten, or what the response contains. The description is not contradictory, but it provides no extra operational context.

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 a single, front-loaded sentence with no filler or repetition. It is appropriately concise, though it borders on being too terse to convey usage context.

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 mutation tool with no output schema and no behavioral notes, the description is thin. An agent would need to infer or experimentally discover what happens if a parameter with the same name already exists, whether the creation is immediately persisted, and how to confirm success. The schema explains inputs well, but the overall context for safely using the tool is incomplete.

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 100%, so the parameters are already fully documented in the input schema. The description adds no semantic information about parameters, but since the schema carries the load, the baseline of 3 is appropriate.

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 uses a specific verb ('Create') and a concrete resource ('user parameter'), and the word 'new' helps distinguish this from sibling tools like set_parameter and delete_parameter. It could be slightly more precise about what makes a parameter 'user-defined', but the core purpose is immediately clear.

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 guidance on when to choose this tool over set_parameter, delete_parameter, or get_parameters. There is no mention of prerequisites, duplicate handling, or whether this is for creating a brand-new parameter versus updating an existing one. The distinction is only implicit in the name.

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