Update Key Value instance

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

The description discloses that changing plan, max memory policy, or persistence mode will restart the instance, which is a key behavioral trait beyond what annotations provide (readOnlyHint=false, destructiveHint=false). It adds useful context about the side effects of certain parameters.

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 relatively short (three sentences) but contains redundancy: 'Update a Key Value instance' is repeated. The first two sentences could be merged. It does front-load the purpose, but the repetition slightly wastes space.

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 basic update action and mentions the restart behavior, which is important context. However, given the tool has 6 parameters (1 required) and no output schema, it omits necessary details such as what happens on success, error conditions, or parameter constraints (e.g., that redisId is required). It is adequate but not complete.

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?

With only 50% schema description coverage, the description should compensate by explaining parameter meanings. It does not—no mention of what each parameter controls beyond the schema. The schema already provides some descriptions, but the description adds no further value for the undocumented ones.

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 that the tool updates a Key Value instance by ID, with the verb 'update' and a specific resource. It also mentions the underlying API call. However, it does not explicitly differentiate from sibling tools like create or delete, which would earn a 5.

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 provides no guidance on when to use this tool versus alternatives (e.g., create or delete). There is no mention of prerequisites, scenarios where update is appropriate, or when to avoid it. The note about restart is behavioral, not usage guidance.

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