Snowflake Undrop Table

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is covered structurally. The description adds the Time Travel mechanism, which is genuinely useful, but omits the critical behavioral limit: undrop only works within the table's retention window and fails past it, and it says nothing about required privileges on the object.

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?

One compact sentence with no filler, front-loaded with the verb. It earns its place, though it is arguably too terse for a recovery operation where the retention constraint is essential rather than optional.

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?

An output schema exists so return values need no explanation, but the definition still leaves out what an agent needs to call this correctly: fully-qualified naming for the sole parameter and the retention-window precondition that determines success or failure.

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% and the description never mentions the single required parameter. For a Snowflake object it matters whether table_name must be a fully-qualified DATABASE.SCHEMA.TABLE identifier or can be resolved from the current context, and neither the schema nor the description clarifies this.

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?

States a specific verb ("Restore") and resource ("recently dropped table") plus the mechanism ("Time Travel"), so the agent knows this is the inverse of snowflake_drop_table. It does not explicitly contrast with snowflake_undrop_schema or snowflake_undrop_database, but the resource in the name disambiguates clearly enough.

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?

"Recently dropped" implies the prerequisite condition for use, but there is no explicit when-to-use/when-not statement and no alternative named. The agent is left to infer that this only applies within the Time Travel retention window rather than being told.

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