MemorySnapshotGet

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

With no annotations provided, the description carries the behavioral burden and does well: it declares the tool read-only, notes the required authorization, and states that it runs outside batch mode. It does not describe error behavior or limits, but the key safety and execution constraints are disclosed.

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 compact, front-loads the read-only/debug tags, and then gives the core purpose in a single sentence. Every phrase contributes useful information without redundancy.

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-only debug tool with five fully described parameters and no output schema, the description is largely complete. It covers the available views and constraints, though it could say more about what a caller receives for each view or when a key is required.

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 100%, so the schema already documents all five parameters including enums and defaults. The description echoes the view options in prose but adds little semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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 identifies a read-only debug tool that retrieves one memory snapshot, and it enumerates the available views (header, overview, ranking, children, references). It distinguishes the resource from the sibling MemorySnapshotList implicitly by saying 'One memory snapshot', though it does not explicitly name the sibling 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?

The description states operational constraints such as needing memory snapshot authorization and running outside batch mode, but it does not explicitly state when to choose this tool over MemorySnapshotList or MemorySnapshotDelta. Usage is implied by the single-snapshot focus.

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