list_boots

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

No annotations are provided, so the description carries the burden. It discloses the per-boot breakdown and a useful interpretation heuristic (many short boots = rebooting device), but says nothing about read-only safety, whether the session parameter defaults to a latest/active session, or ordering. Output schema exists, so return values need limited explanation.

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?

Two tight sentences, front-loaded with the resource and its contents, followed by the diagnostic hook. No redundant restatement of the name; slightly informal phrasing but every clause earns its place.

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?

The output schema covers return values and the description adds a diagnostic interpretation, but the undefined session parameter and its default behavior leave a real gap for an agent deciding how to call it. Adequate but incomplete for a session-scoped listing tool.

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 single 'session' parameter has 0% schema description coverage, and the description never mentions it — not what a session identifier looks like nor what happens when the optional parameter is omitted (default null). With low coverage the description should compensate but adds nothing 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?

States a specific verb+resource ('Boot cycles in the session') and enumerates what each entry contains (start time, line/error/crash counts). It is distinguishable from siblings like query_logs or summarize_session, though it does not explicitly name an alternative.

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?

Gives a concrete diagnostic trigger: 'check this first when behavior looks wedged,' which tells the agent when this tool is the right entry point. It stops short of naming an alternative tool or exclusion, so it is clear context rather than full when/when-not guidance.

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