artifact_list_sessions

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

With no annotations present, the description carries the full burden and does so reasonably: it declares read-only local inspection, no side effects, and that credentials come back masked. It stops short of stating whether sessions come from a local cache file or remote registry, which would matter for trust in the output.

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?

Front-loaded with the core action in the first sentence and organized under clear labels, so an agent can scan it quickly. There is mild redundancy between 'Read-Only local inspection' and 'Side Effects: None', which cost it a point.

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?

An output schema exists, so return values need not be described, and with no inputs the description has little else to cover. It adequately supports correct invocation, though it leaves the notion of a 'session' versus a connection undefined relative to artifact_connect/artifact_disconnect.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The schema is empty and fully self-explanatory.

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 names a specific verb and resource ('List all active and cached registry sessions') plus the scope of what is returned ('masked credentials'), which is enough to distinguish it from siblings like artifact_list_repositories or artifact_status. It is clear but does not explicitly contrast with those near-neighbors.

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 'When to Use' line gives a concrete trigger: determining which sessions are configured before executing workflows. That establishes context well, but no exclusion or named alternative (e.g., 'use artifact_connect to add one') is offered, so the agent must infer when not to call it.

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