step_in

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

With no annotations, the description caries full burden but only states the action without explaining side effects (e.g., what happens when no function call exists) or prerequisites (e.g., active session).

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?

The description is a single, efficient sentence with no redundant words, though it could be slightly expanded for context without harming conciseness.

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 no output schema and 20 sibling debug tools, the description lacks details about preconditions (e.g., paused state), return values, or differentiators, making it incomplete for effective selection.

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 coverage is 100% with adequate descriptions ('Optional thread ID', 'Debug session ID'), but the description adds no additional meaning beyond what the schema provides, earning a baseline score.

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 'Step into the next function call' uses a specific verb ('step into') and resource ('function call') that clearly distinguishes it from sibling tools like step_over and step_out.

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?

No guidance is provided on when to use step_in versus alternatives like step_over (skip function) or step_out (return to caller), leaving the agent to infer usage from the name alone.

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