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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds ordering and return fields, which is useful but not extensive. It does not mention pagination, error behavior, or empty results. Given the annotations carry the safety profile, a 3 is appropriate.

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 concise, well-structured with clear sections (Parameters, Returns), and every sentence provides value. It is front-loaded with the core action and immediately lists the return format. No wasted words.

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?

With no output schema, the description compensates by naming the exact fields (sessionId/status/udid/createdAt/stoppedAt) and ordering. This is sufficient for a simple list tool. It lacks details on status values or error handling, but these are not critical for invocation.

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?

There are zero parameters, and the schema is empty. The description adds 'Parameters: None' which echoes the schema. Per the baseline rule for 0 params, a score of 4 is correct since no parameter explanation is needed beyond the schema already being 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 description clearly states the verb ('List'), the resource ('all HangBuster capture sessions'), and the ordering ('newest first'), along with the output fields. This distinguishes it from siblings like hang-get-details, which presumably fetches a single session. The purpose 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 implies usage (list all sessions) but does not explicitly mention alternatives or when not to use it. Sibling tools like hang-start, hang-stop, and hang-get-details exist, but no guidance is given on choosing this tool over them. The context is clear but lacks explicit routing.

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