zadd

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

No annotations provided. Description covers the basic operation, optional expiration, and return value. However, it omits standard Redis ZADD behavior (e.g., updating score if member exists) and effects of expiration on the key.

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?

Short, front-loaded with the main purpose. Uses a clear structured format with Args and Returns. Could be slightly more concise but no wasted sentences.

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?

Adequate for a simple Redis command. Lacks details on edge cases (e.g., duplicate member, error messages) and does not describe the return format beyond 'confirmation or error'. Output schema exists but no details provided.

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 has 0% description coverage. Description adds brief explanations for each parameter (key, score, member, expiration in seconds), adding meaning beyond the schema property names, though still minimal.

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 states the verb 'Add' and resource 'member to a Redis sorted set' with optional expiration. It distinguishes from siblings like zrange and zrem but not from sadd or other add operations.

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 (e.g., sadd for sets, zadd for sorted sets). Missing context about prerequisites or scenarios.

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