iyke_kv_set

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

Discloses size caps (64 KB per value, 1 MB per scope) and default scope behavior. No annotations exist, so description carries full burden. Could be improved by mentioning whether existing values are overwritten or the return value on success/failure.

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?

Two sentences, no redundancy. Front-loaded with the primary action and key constraints. Every word serves a purpose.

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 no output schema and sparse schema descriptions, the description covers the essential behavioral aspects: purpose, size limits, alternative tool, and default scope. A minor gap is the lack of return value description, but for a simple set operation this is adequate.

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 0% schema description coverage, the description adds some meaning: 'value' must be a JSON object (implied by 'JSON value'), and 'scope' defaults to active project. However, it does not explain what 'key' should be (e.g., string format) or constraints on 'value' beyond JSON.

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?

Clearly states the tool stores a small JSON value at a scope+key, distinguishing it from sibling tools like iyke_kv_get, iyke_kv_delete, and iyke_kv_list. The verb 'store' and resource 'JSON value' are specific and unambiguous.

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?

Explicitly provides guidance on when not to use this tool: 'For larger durable text, use scratchpads.' Also mentions scope default behavior, helping the agent decide between this and alternatives.

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