dbgprobe.elf.info

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

No annotations provided; description carries burden. Discloses null return when no ELF attached, which is good. Does not disclose if the operation is read-only or requires a connected session, but it is implied by context.

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?

Single sentence plus a note about null return. No wasted words, front-loaded with main purpose.

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?

Lists fields returned (file path, symbol count, entry point, sections) but no types or structure. No output schema, so description should be more detailed. Given 1 param and no output schema, it is moderately complete.

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 has one parameter (session_id) with 0% description coverage. The overall description does not explain session_id beyond its name; no format or semantics added. The description fails to compensate for missing 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?

Clearly states verb 'Get' and resource 'ELF metadata for a session', and lists specific fields returned. Distinguishes from siblings like dbgprobe.elf.symbols (symbol enumeration) and dbgprobe.elf.lookup (symbol lookup).

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?

Implies usage when ELF metadata is needed, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives. Does not mention alternatives like dbgprobe.elf.symbols for detailed symbol info.

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