quire.putStorageValue

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

Description adds the key behavioral trait 'Overwrites any existing value with the same name' beyond the idempotentHint annotation. No contradictions. Could mention persistence or size limits.

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?

One concise sentence of 15 words, front-loaded with the core purpose. No wasted 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?

For a simple put operation with 2 parameters and no output schema, the description covers the core behavior. Lacks error handling or interaction details, but sufficient for most cases.

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 100% (both name and value have descriptions). Description adds no extra parameter info, so baseline 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?

Clearly states 'Store a value in Quire's key-value storage' with a specific verb and resource, and distinguishes from siblings like getStorageValue, deleteStorageValue, and listStorageEntries by mentioning the overwrite behavior.

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?

Does not explicitly state when to use this tool vs alternatives (e.g., getStorageValue for retrieval, deleteStorageValue for removal). No prerequisites or context provided.

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