Lists recorded automatic-launch metadata from a saved snapshot, including enabled status and source, so you can review startup items without changing system settings.
List recorded automatic-launch metadata from a saved snapshot, including enabled status and source. Unknown status is preserved. limit is 1–100.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| snapshot_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by noting that unknown status is preserved and that limit is bounded to 1–100. It does not describe ordering, pagination, or return shape, so it adds some value but not rich behavioral detail.
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 short, front-loaded with the core purpose, and avoids unnecessary repetition. The added notes about unknown status and the limit range are relevant, though the phrasing is terse rather than fully polished.
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 simple two-parameter read-only list tool with no output schema, the description gives enough context: what is listed, what fields are included, how unknown status is handled, and the limit range. It could be more complete by mentioning snapshot acquisition or pagination, but the essential invocation context is present.
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 description coverage is 0%, so the description must compensate. It adds the important constraint that limit is 1–100 and gives context that snapshot_id refers to a saved snapshot, but it still does not fully explain snapshot_id format or other parameter expectations.
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: listing recorded automatic-launch metadata from a saved snapshot. It also specifies included fields, enabled status and source, making the purpose clear. It does not explicitly distinguish this tool from sibling list tools such as list_findings or list_unusual_destinations, so it stops short of a 5.
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 the tool operates on a saved snapshot but gives no explicit guidance on when to use it versus alternatives like list_findings, list_unusual_destinations, or take_snapshot. There are no stated prerequisites or exclusions beyond the snapshot reference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.