switch_my_bt

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

No annotations provided, so description carries full burden. Discloses important behavioral limitation (misses first address) and implementation method (walking frame pointer chain). Implies read-only operation via 'Print', though could explicitly state no 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?

Two sentences, zero waste. First sentence defines function and mechanism; second provides critical limitation and workaround. Perfectly front-loaded.

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?

Without output schema, the description adequately explains the output format ('absolute addresses') and a key limitation. Given the tool's narrow scope (0 parameters, simple output), this is sufficient, though mentioning read-only safety would strengthen it further.

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?

Input schema has zero parameters. Baseline score of 4 applies as there are no parameters requiring semantic clarification.

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 the tool prints backtraces as absolute addresses using frame pointer chain walking. Specific about method and output format. However, it does not explicitly differentiate from sibling 'switch_my_bt2', which appears to be a variant.

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?

Provides clear guidance about a key limitation ('Often misses the first address') and explicitly recommends an alternative command ('p/x $lr') for that case. Lacks explicit comparison to sibling tools like 'switch_my_bt2' for when to use which variant.

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