sessions_list_agents

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

With no annotations provided, the description carries the full behavioral burden, yet it only says 'List', which implies a read operation. It does not disclose pagination behavior (continuation_token), default limits, or what happens when a session doesn't exist, leaving important behavioral traits unstated.

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?

A single sentence with a code-formatted path; efficient and front-loaded with the resource scope. It is appropriately sized, though it could add pagination context without becoming verbose.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It omits pagination semantics, error behavior, and how this relates to sibling agent-retrieval tools, leaving an agent to guess at invocation details beyond session_id.

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 0%, so the description must compensate. It ties session_id to the URL path but says nothing about limit or continuation_token, leaving two of three parameters semantically unexplained. The description only partially covers what the schema lacks.

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 states a specific verb ('List'), a precise resource ('agent IDs'), and an explicit scoped path (`sessions/<session_id>/agents/`). This clearly distinguishes it from siblings like registry_list_agents (registry-scoped) and sessions_list (session list), so an agent can disambiguate without opening schemas.

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?

Usage context is implied by the path structure: use this when you need agent IDs inside a specific session. However, there is no explicit when-to-use, when-not-to-use, or mention of alternatives such as sessions_get_agent_json for full agent objects.

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