step_into

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

Describes blocking behavior, required state (STOPPED), and result state (stopped inside function). No annotations to contradict, and description adds valuable behavioral context beyond schema.

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?

Well-structured with sections for purpose, state requirement, usage, arguments, and escape hatch. Each sentence is informative, though slightly verbose; could be tightened.

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?

Covers essential aspects: blocking, state management, argument usage, and relation to sibling tools. Lacks return value details due to no output schema, but this is acceptable given the tool's nature.

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 0%, but description explains both parameters: thread_id (optional, uses current thread) and target_id (optional, derived from get_step_in_targets). Adds meaning beyond the schema's titles and types.

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 'Step into the next function call' and explains it enters the called function. Distinguishes from sibling tools like step_out and step_over by mentioning when to use them.

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 explicit guidance: use when investigating inside a called function, recommends get_step_in_targets for multiple calls on one line, and advises step_out to return. Does not explicitly state when not to use, but provides sufficient context.

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