DebugGetVariables

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

With no annotations, the description carries the burden and does so reasonably: it discloses read-only nature, the stopped-debuggee prerequisite, and the batch-mode restriction. It omits failure behavior (e.g., what happens if the debuggee is not stopped) and any hint about response shape, keeping it short of a 5.

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 short sentences, front-loaded with the read-only/debug tags and the core purpose, followed by preconditions. No filler; every clause conveys actionable information.

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 read tool with a fully described schema and no output schema, the description covers the essential precondition and mode. The detail parameter in the schema explains return granularity, so the missing return-value discussion is largely compensated.

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 100%, so all four parameters including the detail enum are fully documented in the schema. The description only echoes the names-vs-parents distinction already present in the schema, adding little beyond baseline.

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 and resource — retrieving variables of a stopped debuggee — and clarifies the two access modes (by name vs. as members of a parent), which separates it from DebugSetVariable. It never names a sibling or an explicit alternative, so it lacks the differentiating routing language 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?

Gives concrete preconditions: a stopped debuggee is required and it must run outside batch mode. That's useful operating context, but there is no guidance on when to prefer names vs. parents beyond the schema, and no exclusion pointing to related tools like DebugGetStack.

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