git-stash-pop

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

The description only mentions 'applies' but fails to disclose that git-stash-pop also removes the stash after applying (destructive behavior). With no annotations provided, this omission is critical.

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 one short sentence, efficient and front-loaded. However, it could be slightly longer to include essential behavioral details without becoming verbose.

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?

The description is incomplete for a simple tool; it omits the fact that the stash is also dropped (pop behavior), error conditions, and does not mention that the tool is safe or destructive. Despite having a single optional parameter, crucial context is missing.

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 single parameter 'directory' is fully described in the schema. The description adds no additional meaning beyond what the schema provides, so baseline score applies.

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 (applies stash) and resource (most recent stash). However, it does not differentiate from siblings like git-stash which may have similar subcommands, and the name implies a specific behavior not fully clarified.

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 on when to use this tool vs alternatives (e.g., git-stash-apply). The description lacks context about prerequisites or scenarios where this tool is appropriate.

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