get_memory_map

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the tool uses `info proc mappings` and works without pwndbg, and that vmmap provides richer output. However, it does not state whether the operation is read-only, what shape the returned mappings take, or how session_id affects the call.

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 with no filler. The core behavior is front-loaded, and the useful alternative pointer is placed second. Every part 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?

For a simple read-style tool this is close to complete, but with no annotations and no output schema, the description should clarify the optional session_id and at least indicate the return format. Those omissions leave a moderate gap for an agent deciding how to invoke it.

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 input schema has one optional `session_id` parameter with no description, and the tool description never mentions it. Since schema description coverage is 0%, the description does not compensate for the missing parameter semantics; only the parameter name and default hint at its purpose.

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 the resource ('memory mappings of the inferior') and the underlying GDB command (`info proc mappings`), while distinguishing it from the richer `execute_command('vmmap')` alternative. It lacks an explicit verb, but the tool name makes the intended action unambiguous.

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 explicitly names an alternative tool/command and gives the condition for choosing it: 'For richer output use execute_command("vmmap").' This provides clear routing guidance and makes the boundary between this tool and the richer alternative explicit.

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