get_callstack

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

With no annotations, description adequately discloses that operation requires halted target, returns complete call chain with arguments and source context. Implicitly read-only, but no explicit safety statement. Lacks mention of permissions or return format details beyond 'formatted'.

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?

Three sentences, front-loaded with purpose, no filler. Prerequisite and output format included efficiently.

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 zero parameters and presence of an output schema, description fully covers tool behavior and expected output. No gaps remain.

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?

Tool has zero parameters; baseline score 4 is appropriate. Description adds no parameter info, but none needed.

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 it retrieves the current call stack with function names and arguments. It distinguishes itself from sibling tools like get_current_function by focusing on the full backtrace.

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?

States prerequisite 'target must be halted', providing clear context for use. Does not explicitly exclude alternatives but the purpose is self-evident. Slight gap in comparing to get_current_function or get_source_location.

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