get_chat_sessions

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

With no annotations, the description should explicitly state that the tool is read-only and does not modify data. It only says 'list', which implies read but doesn't confirm. No disclosure of authentication needs, rate limits, or data freshness.

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 very short (one sentence) with a dash separator, but the '[query]' appears to be a placeholder or incomplete. While concise, the structure is slightly marred by this unclear token.

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 output schema and no annotations, the description should explain ordering, pagination, and default behavior (e.g., what 'recent' means). It fails to fill these gaps. The presence of a sibling with a similar name further demands differentiation, which is absent.

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 100% with parameter descriptions, so the bar is neutral. The tool description adds the context of 'recent sessions', but does not clarify parameter interactions or formats beyond what the schema already provides. Score at baseline.

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 that the tool lists recent web chat sessions, specifying the resource (web chat widget sessions) and action (list). However, it does not differentiate from the sibling tool 'get_plugin_chat_sessions', which could cause confusion. The '[query]' placeholder is unclear.

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 like 'get_plugin_chat_sessions' or 'search_conversations'. It lacks context on prerequisites, scope (e.g., user or workspace filtering), or limitations.

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