list-sessions

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

The description mentions the expected return type and ordering, but lacks details on pagination, error behavior, or authentication requirements. Since annotations are absent, the description carries full burden but covers only basic behavior.

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 concise with three sentences and an example. It is front-loaded with the core purpose and contains no unnecessary content.

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 the lack of annotations and output schema, the description is too minimal. It does not specify error handling, pagination, or clarify that project_identifier is likely required despite being not marked as such in the schema.

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 schema has 0% description coverage, and the description does not explain each parameter individually. The example implies the use of limit and project_identifier, but 'order' and the necessity of project_identifier are not clarified.

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 sessions for a project, and defines sessions as conversation flows grouped across traces. It is specific enough to distinguish from sibling tools like list-traces, though it could explicitly contrast them.

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 an example usage but does not give explicit guidance on when to use this tool versus alternatives. No prerequisites or exclusions are mentioned.

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