edb_stack_push

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

Discloses key side effects: modifies stack and register state, beyond the destructiveHint annotation. Provides concrete details (decrements RSP) that help the agent understand what changes.

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?

Extremely concise and front-loaded. First sentence captures core action. Args and returns sections are minimal but sufficient. No wasted words.

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?

Adequate for a simple push operation but missing return semantics. The output schema indicates a string result, but the description only says 'str: Result' without clarifying what the result contains (e.g., success message).

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 parameter 'value' is described in the schema with examples, and the description repeats similar info. Schema coverage is adequate, so the description adds minimal extra meaning beyond the schema.

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 clearly states the action: 'Push a value onto the program stack' with specific mechanics (decrements RSP, writes value). It distinguishes from siblings like edb_stack_pop and edb_stack_modify by focusing on pushing.

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 explicit guidance on when to use this tool vs alternatives. The description mentions a UI equivalent but lacks context for when pushing is appropriate compared to other stack operations.

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