list_bisect_sessions

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

With no annotations provided, the description carries the full behavioral burden, and it does little: 'active' hints at a filtering behavior, but there is no statement about read-only safety, authorization, tier gating, or what a session record contains. The trailing marketing block implies a Kiln Pro requirement without clarifying whether this specific tool is gated, which actively muddies the picture.

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 first sentence is well-formed and front-loaded, but it is followed by three lines of unrelated upsell copy (calibration, textures, upgrade URL) that consume roughly three-quarters of the text and add zero operational value. The useful content is drowned by advertising.

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?

There is no output schema and no annotations, so the description must convey what comes back, and it does not — no mention of session fields, ordering, or pagination. For a single-optional-param list tool the schema is thin enough that one more sentence on return shape would have closed the gap.

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 coverage is 0% and artifact_type is a bare string with no title or enum, but the description supplies the three accepted values (design / preset / feature), which is real added meaning. It stops there, though — nothing about case sensitivity, default behavior when omitted, or whether values outside the set error or return empty.

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 opening sentence names a specific verb and resource ("List active bisect sessions") and scopes it with an optional artifact-type filter, which separates it from the bisect_start/bisect_good/bisect_bad action siblings. It does not explicitly name which sibling to use instead, but the purpose itself is unambiguous.

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 says what the tool lists but never states when an agent should reach for it versus the surrounding bisect workflow tools (bisect_current, bisect_start, bisect_end), nor any prerequisite such as an in-progress session. Usage is only inferable from the tool name.

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