rpush

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

With no annotations, the description must disclose behavioral traits, but it only states the basic operation. It omits details such as whether the list is created if it doesn't exist, what happens on error, idempotency, or the return value (though an output schema may exist). The mutation implied by 'push' is the only behavioral hint.

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 a single, front-loaded sentence that efficiently communicates the core action and optional parameter. No unnecessary words or redundancy, earning a high score for conciseness.

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 annotations and a 0% schema coverage, the description is insufficiently complete. It lacks behavioral context like list creation behavior, error conditions, return value semantics (though output schema may help), and does not leverage sibling tool names to clarify usage boundaries.

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 the description should compensate. It adds meaning to 'value' (the element to push) and 'expire' (optional TTL), but does not explain 'name' (the list key) or the allowed data types for 'value' as defined in the schema. Partial coverage, leaving gaps.

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 clearly states the action ('Push'), the resource ('a value onto the right of a Redis list'), and an optional feature ('set an expiration time'). It distinguishes this from the sibling tool 'lpush' by specifying 'right', and from other list operations by naming the verb 'push'.

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 guidance on when to use rpush versus alternatives like lpush or other list commands. It does not mention prerequisites, when not to use it, or any specific context where this tool is more appropriate.

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