get_call_stack

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

Annotations already indicate readOnly and idempotent. Description adds that the thread must be in STOPPED state, describes a diagnostic env var, and an escape hatch. Does not contradict annotations. Adds valuable behavioral context beyond what annotations provide.

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 extremely concise: one sentence for purpose, three bullet points for state, diagnostic, and escape hatch. Every sentence adds value, and it's well-structured with headings.

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?

No output schema, so description should explain return values, but only mentions 'Returns frame_id values needed for get_scopes()'. Missing parameter explanations and comprehensive return format. Despite annotations, the description is insufficient for a tool with undocumented parameters.

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 2 parameters (thread_id, levels) with 0% description coverage. Description does not explain what these parameters mean or how they affect the call stack retrieval. Without any explanation, the agent cannot infer correct usage beyond their names.

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 'Get the call stack for a thread' with a specific verb and resource. It distinguishes itself by noting that it returns frame_id values needed for get_scopes, and references diagnostic env var and escape hatch, making the purpose clear.

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 'State: STOPPED required', which is a critical usage prerequisite. Also mentions the dependency on get_scopes for further use of returned frame IDs. Provides an escape hatch reference. Lacks explicit 'when not to use' or alternatives, but the context is clear.

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