dbgprobe.elf.lookup

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

Discloses the bidirectional lookup behavior and requirement. With no annotations, the description carries the full burden; it could mention error cases (e.g., if both or none provided) or return format.

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 sentences, no waste, front-loaded with the core concept. Every word 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?

Covers the essential functionality for a simple 3-param tool. Could hint at return format, but not necessary given low complexity and no output schema.

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?

Adds meaning beyond schema by explaining the direction of lookup for 'symbol' and 'address'. The schema descriptions are basic, so this adds value. session_id is not mentioned in description but is covered by schema.

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 states 'Bidirectional symbol lookup' and explains the two modes (symbol-to-address, address-to-name+offset). This distinguishes it from siblings like dbgprobe.elf.symbols which lists all symbols.

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?

Explicitly states 'Exactly one is required' and explains the mapping for each input. However, it does not explicitly differentiate when to use this vs. dbgprobe.elf.symbols for listing.

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