lpush

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

Discloses the core write operation and optional expiration, but does not mention return value (list length), error handling for non-list keys, or TTL unit. Without annotations, description carries full burden and is moderately transparent.

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?

Single sentence, 14 words, no redundancy. Front-loaded with core action and optional feature. Efficient.

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?

Tool has 3 parameters, no annotations, and output schema exists but description doesn't mention return value (list length). Lacks details like TTL units or effect on existing TTL. Adequate but incomplete for a simple tool.

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 coverage is 0%, so description should add meaning. It explains 'value' as the data to push and 'expire' as optional TTL, but 'name' (the list key) is only implied. Partially compensates but not fully explicit for all parameters.

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 it pushes a value onto the left of a Redis list and optionally sets expiration, distinguishing it from rpush (right push) and other list operations. The verb 'push' and resource 'Redis list' are specific.

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 explicit guidance on when to use this tool vs alternatives like rpush, lset, or lpush with expire. Only implicit differentiation from sibling names. No when-not or alternative comparisons.

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