refresh_catalog

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

No annotations are provided. The description discloses scanning all databases, cache TTL, and parameter effects (force, resume). However, it does not explicitly state that the operation is non-destructive (read-only) or mention any permission requirements. It provides basic behavioral context but lacks some depth.

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 concise: one introductory paragraph, a bullet list of when to use, and a parameter list. It is front-loaded with the primary action and every line adds value. 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?

The description covers the tool's core behavior (scanning, caching, 5-day TTL), usage scenarios, and parameters. It assumes an output schema exists (per context) but doesn't describe it, which is acceptable since output schema is provided separately. It could elaborate on what 'checkpoints' are, but overall it's sufficient for the tool's complexity.

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% (parameters have no descriptions in schema). The description adds meaning: force means 'force refresh even if cache is not expired' and resume means 'resume from checkpoints if they exist'. This adequately explains the boolean parameters beyond their names and defaults.

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 'Refresh the schema catalog by scanning all accessible Snowflake databases' with specific actions (scanning, building index, cache). It distinguishes from sibling tools (which are all query/table-level tools) by being a meta-catalog operation.

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?

The description explicitly lists three use cases: first connection, schema changes, and cache expiry. While it doesn't mention when NOT to use, the use cases are clear and cover the main scenarios. No alternative tools are named, but siblings are sufficiently different.

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