create_session

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

No annotations are provided, so the description carries the full burden. It never says whether file_path or pid must be supplied, whether they are mutually exclusive, what happens on conflict, whether sessions are resource-limited, or that write_mode/debug_mode change the session's safety profile substantially. Only the bare flag names are echoed.

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?

Front-loaded purpose sentence followed by an efficient Args list and a one-line Returns. No padding, though the Returns note is redundant given an output schema exists.

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?

An output schema exists, so return values need not be described. But for a session-creation tool with zero annotations, five parameters, and no required fields, the description omits the critical constraint of how file_path and pid relate, leaving an agent to guess.

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, and it does list all five parameters. However most entries merely restate the name ('Enable write mode', 'Enable debugger mode'), adding little real semantics; only session_name's auto-generation note adds information.

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+resource ('Create a new Radare2 session') that is immediately distinct from read/list siblings. It does not, however, differentiate itself from close_session or switch_session beyond the verb, and gives no indication of what a session enables.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The file_path vs pid pair is clearly an either/or choice that determines what the session attaches to, yet the description never states this or says whether one is required.

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