iccap_sessions_list

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses a meaningful behavior (not exposing authentication tokens) but does not mention whether the operation is read-only, what 'live' precisely entails, or any other side effects or requirements.

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 immediately states the action and resource. The extra clause about authentication tokens is relevant and non-redundant, earning its place without adding fluff.

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 zero-parameter list tool, the description is adequate but not complete. It does not describe the shape of the returned list (e.g., session IDs, names, status) or how the results connect with related tools like iccap_session_select. Since there is no output schema, the description could have provided more context.

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, so the empty input schema fully describes the parameter space. Per the baseline for 0 parameters, the description does not need to compensate for missing parameter documentation, and the score reflects that.

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 a specific verb ('List') and resource ('live IC-CAP sessions'), clearly stating the tool's function. The qualifier 'without exposing authentication tokens' adds a differentiating detail that helps distinguish it from other session-related tools like iccap_session_select.

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 such as iccap_session_select or iccap_job_list. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent to infer usage entirely.

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