List Domain Sessions

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

Annotations already declare readOnlyHint=true, and the description confirms this read operation. It adds that sessions are org-scoped and stored via metalift_seed_session, but it does not disclose behavior such as pagination, ordering, or what fields are returned. This is a modest addition beyond the annotation.

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 a single, front-loaded sentence that includes only essential information: the verb, the resource, and the source. There is no wasted text.

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 parameters and a simple listing function, the description is adequate. It specifies the scope ('org-scoped') and source ('stored via metalift_seed_session'), though it does not detail the contents of the returned list. Given the simplicity and annotation support, it is sufficiently complete.

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 tool has zero parameters and an empty schema, so the description has nothing to add. The baseline score for 0 params is 4, which is appropriate here.

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 uses the specific verb 'List' and identifies the resource as 'org-scoped browser sessions,' clearly distinguishing this from scraping, crawling, and strategy tools. It also references the related seed tool, clarifying its role in the workflow.

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 clear context: this tool lists sessions stored via metalift_seed_session, implying use after seeding or to inspect existing org-scoped sessions. It does not explicitly mention when not to use it or alternatives like list_strategies, but the context is sufficient for typical use.

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