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

Even with readOnlyHint=true and openWorldHint=false in annotations, the description adds meaningful behavioral detail: sessions include full history, document chunks and tool calls are returned as references only, results are paginated, and ordering is by start time descending. This goes beyond the annotations and helps set expectations for the response shape.

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 compact and front-loaded with the core purpose, then lists filters and key output behavior. It is only three sentences and contains no fluff, though there is a minor formatting issue ('content.Returns') and the long filter sentence could be more scannable.

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 read-only list tool with an output schema and eight optional parameters, the description covers the essential behavior: filtering, pagination, ordering, and the reference-vs-full-content distinction. It does not explicitly mention the time_filter parameter in prose, but the schema provides a detailed description for that parameter, so the overall context is sufficient.

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 description coverage is 75%, so the schema already documents most parameters. The description names several filters (interaction types, embed types, answer types, tool IDs, search query) but mostly restates what the schema covers and notably omits time_filter. It does add a little context by grouping the filter options, but does not significantly compensate for the undocumented page/limit parameters.

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 opens with a specific action and resource: 'List sessions for application,' and then enumerates the available filters. It is clearly distinct from siblings like read_session_detail and list_tools because it targets the plural 'sessions' resource with listing behavior, though it does not explicitly name sibling alternatives.

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 implies usage: call this when you need to list or filter sessions, and the note that document chunks and tool calls are only references suggests it is not for fetching full content. However, it never explicitly states when to prefer read_session_detail or read_chat_request_documents/tool_calls, so usage guidance is implied rather than direct.

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