Manage debugger session metadata

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses one important behavior: 'Loading never silently recreates breakpoints,' which is valuable context. However, it does not mention other side effects, permission requirements, or what happens on save/export, leaving significant gaps in transparency.

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 just two sentences, front-loaded with the core action list. Every word earns its place, and the additional behavioral caveat is relevant and non-redundant.

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 tool has 4 parameters, no annotations, no output schema, and 0% schema coverage. The description is too brief to fill these gaps: it does not explain return values, side effects beyond the loading caveat, or the purpose of optional parameters. This is a moderately complex tool that needs a richer description.

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 names the actions (save, list, load, export) which map to the 'action' enum, but does not explain the meaning of 'name' or 'targetSessionId', nor how they relate to the session. This leaves half the parameters ambiguous.

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 tool's function: 'Save, list, load, or export in-memory debugger metadata for one Raw session.' It uses specific verbs and a specific resource, distinguishing it from sibling debugger tools like pause/step/evaluate, which operate on execution state rather than session metadata.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when a different debugger tool might be more appropriate. The only caveat ('Loading never silently recreates breakpoints') is a behavioral note, not usage guidance.

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