filter_sessions

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While '筛选' (filter) implies a read operation, the description doesn't specify whether this is a read-only tool, what permissions are required, how results are returned, or any rate limits. It provides minimal behavioral context beyond the basic operation.

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 extremely concise with just two sentences that directly state the purpose and parameters. There's no wasted text, though some might argue it's too brief given the lack of annotations and output schema. The structure is front-loaded with the core purpose first.

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, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't explain what the tool returns (filtered session objects? just counts?), how results are structured, error conditions, or authentication requirements. For a filtering tool with two parameters, more context is needed.

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 description explicitly lists both parameters with Chinese explanations ('是否有未读' for has_unread meaning 'whether has unread', '是否免打扰' for ismute meaning 'whether muted'). With 0% schema description coverage, this adds meaningful semantic context that the schema lacks. However, it doesn't explain parameter formats, valid values, or how they interact.

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 ('筛选' meaning filter) and resource ('会话列表' meaning session list), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'get_sessions' or 'get_unread_sessions', which appear to be related session retrieval tools.

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 this tool versus alternatives. With sibling tools like 'get_sessions' and 'get_unread_sessions' available, there's no indication of when filtering is preferred over direct retrieval or how this tool complements other session-related tools.

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