redis_srem

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

With no annotations provided, the description must disclose all behaviors. It correctly identifies the tool as destructive (removing a member) and mentions a blocking condition under readOnly mode. However, it does not describe what happens if the member does not exist (e.g., returns 0) or whether the operation returns a count or a success indicator. The lack of output schema further reduces transparency.

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 concise with two short sentences. The first sentence clearly states the core action, and the second adds a critical constraint. There is no extraneous information, and every sentence earns its place.

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 tool (remove a member from a set), the description covers the core action and a key constraint. However, given the low schema coverage and no output schema, the description remains incomplete. It does not explain the return value (e.g., integer 1 if removed, 0 if not present) or what happens on errors (e.g., wrong type or key not a set). This limits the agent's ability to handle responses correctly.

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?

The input schema has 33% description coverage (only connectionId has a description). The description does not explain the semantics of 'key' (set name) or 'member' (the element to remove) beyond the tool's purpose. For example, it does not specify valid formats or constraints. The schema itself leaves key and member without descriptions, so the description should compensate but fails to do so.

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 'Remove a member from a set', specifying the verb (remove) and resource (member from a set). This distinguishes it from sibling Redis set tools like redis_sadd (add), redis_smembers (get all), and redis_sismember (check membership).

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 only mentions a blocking condition ('Blocked when that connection's own readOnly mode is enabled') but provides no guidance on when to use this tool versus alternatives. It does not compare with other set operations or state prerequisites. For example, it does not suggest using redis_sadd for adding or redis_sismember for checking membership.

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