pwndbg_contextwatch

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

No annotations provided, so description must disclose behavior. It mentions that the expression is evaluated and displayed on every context refresh, but does not specify persistence, removal process, or side effects.

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?

Description is concise and well-structured: lead sentence, alias/source, behavior, then clear arg explanations. No redundant 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?

Given the presence of output schema, return value explanation is not needed. Description covers all parameters and behavior adequately. A link to documentation provides additional context.

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?

With schema_description_coverage at 0%, the description adds essential meaning: it identifies session_id as UUID, expression with examples like '$rax', and cmd with display commands. This fully compensates for the lack of schema descriptions.

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?

Description clearly states 'Add a watched expression to the context display' and explains that the expression is evaluated and displayed on each context refresh. It distinguishes from siblings like pwndbg_contextunwatch by focusing on adding, not removing watches.

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?

Description provides examples for expression and optional cmd, but lacks explicit guidance on when to use this tool versus alternatives (e.g., pwndbg_contextunwatch). No exclusion criteria or prerequisites mentioned.

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