Git stash

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

The description explicitly calls out that pop and drop are destructive, adding specificity beyond the generic destructiveHint annotation. It also implies list and push are non-destructive, which is useful behavioral context, though it does not describe other side effects like working-directory 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?

The description is very short and front-loads the core operations, with the destructive warning placed second. It is concise with no filler, though the fragment 'Stash list/push/pop/drop' is slightly telegraphic.

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?

With four parameters, no schema descriptions, and a destructive-capable tool, the description is too sparse to fully guide invocation. It omits how path/index/message are used, what each action does, and any prerequisites or side effects beyond the destructive warning.

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 description coverage is 0%, so the description carries the burden of explaining parameters. It only surfaces the valid action values (list/push/pop/drop) but does not explain the meaning of path, index, or message, nor the relationships between action and these parameters.

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 names the Git stash resource and the four supported operations (list/push/pop/drop), which is clear enough for an agent to identify what the tool does. It does not explicitly differentiate this tool from sibling Git tools, but the action list makes the purpose reasonably unambiguous.

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?

There is no guidance about when to use this tool versus alternatives like git_show, git_checkout, or other git tools, nor any conditions for choosing list vs push vs pop/drop. The description implies stash management but does not state any usage context or exclusions.

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