put-global-parameter

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

Annotations indicate write operation (readOnlyHint=false) and open world hint (openWorldHint=true). Description adds no extra behavioral details, such as whether the operation is idempotent, requires specific permissions, or what happens on name collision.

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?

Description is extremely concise (one phrase), but borderline under-specified. Could benefit from a second sentence to add context without losing conciseness.

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?

No output schema and minimal description. Lacks explanation of global parameter concept, required permissions, effect on existing parameters, and return behavior. For a two-parameter tool with 0% schema coverage, the description is insufficient.

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 description coverage is 0%, so description must compensate. It mentions 'name' and 'value' but does not explain that value can be any type, constraints on name, or expected formats. The schema defines value as {} (any), but description adds no semantic clarity.

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?

Description clearly identifies verb (create or update) and resource (global parameter), distinguishing it from sibling tools like delete-global-parameter, get-global-parameter, and list-global-parameters. However, it does not differentiate from put-parameter, which updates a regular parameter on a vhost.

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, such as put-parameter for vhost-scoped parameters or delete-global-parameter for removal. The context of global vs. regular parameters is not explained.

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