step_over

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

With no annotations, the description must disclose behavioral traits. 'Step over' does not clarify that it executes the current line without stepping into functions, nor does it mention side effects, permissions, or return behavior. The description is completely inadequate for understanding the tool's behavior.

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 extremely concise (two words) but this is under-specification, not efficient conciseness. It fails to provide essential information that would justify its brevity.

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 the tool's simplicity (one parameter) but the importance of its role in debugging alongside siblings, the description is wholly incomplete. It does not explain the action, the parameter, or the expected outcome. An AI agent cannot reliably select or invoke this tool based on this description.

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?

The input schema has 0% description coverage and one required parameter 'sessionId' with no description. The tool description does not mention or explain this parameter, leaving its purpose and format entirely unspecified.

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 over' is a near tautology of the tool name. While it identifies the action as a debugging step operation, it provides no additional context to differentiate it from siblings like 'step_into' or 'step_out'. It lacks specificity about what resource or state is affected.

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 this tool versus alternatives. The description does not mention conditions, prerequisites, or exclusions. Sibling tools exist with related actions ('step_into', 'step_out'), but the description offers no differentiation.

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