iyke_kv_delete

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

The description states idempotency, but lacks other behavioral details such as error handling, permissions, or effects on related data. With no annotations, this is somewhat adequate but minimal.

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 extremely concise, with only two sentences that convey the purpose and a key behavioral trait. No unnecessary words.

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 core operation and idempotency, but for a delete tool, missing details about scope parameter and what happens when key doesn't exist. Not fully complete but functional.

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?

No parameter descriptions are provided in either the schema or the description. With 0% schema description coverage and no mention of parameters in the text, the agent has no guidance on what 'key' and 'scope' represent.

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 specific verb 'Delete' and resource 'KV entry', clearly distinguishing from sibling tools like iyke_kv_get and iyke_kv_set.

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 usage context or comparisons to sibling tools. No when-to-use or when-not-to-use information.

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