expire

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

No annotations provided, and description only states it sets expiration and returns success/error. It does not disclose key behavioral traits: whether it works only on existing keys, overwrites existing TTL, or behavior for expired keys.

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?

Description is succinct with clear Args and Returns sections. Minor verbosity: blank line after first sentence not needed. Otherwise well-structured.

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 output schema exists and tool complexity is low, description covers core purpose and parameters. However, missing behavioral details (e.g., key existence handling, overwrite behavior) reduce completeness.

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?

Input schema has 0% coverage, so description compensates by defining both parameters: name as 'the Redis key' and expire_seconds as 'time in seconds after which the key should expire'. This is adequate but basic.

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 'Set' and the resource 'Redis key' with the specific action 'expiration time'. This distinguishes it from sibling tools like 'set' or 'delete'.

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, no prerequisites or when-not-to-use advice. It simply describes the operation without context.

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