refresh_catalog

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

No annotations are provided, so the description must disclose behavioral traits. It mentions scanning all databases and a 5-day cache TTL, and explains the 'force' and 'resume' parameters. However, it does not describe potential side effects (e.g., performance impact) or authentication needs.

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, well-structured with a brief intro, a bulleted usage section, and parameter details. Every sentence adds value; no redundancy.

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?

Given no output schema, the description gives some idea of the output ('build a comprehensive index...'). It covers the tool's core behavior and parameters well. Missing details on what the catalog index looks like post-refresh or whether other tools immediately benefit.

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 input schema has 0% description coverage (no property descriptions), but the tool's description includes a bulleted list explaining both parameters, their meanings, and defaults. This compensates well for the schema gap.

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', which is a specific verb+resource combination. It distinguishes from siblings like describe_table, execute_query, and find_tables by focusing on catalog maintenance rather than data access.

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?

Explicitly lists three use cases: first connection, after schema changes, and when cache expires. Also mentions the 5-day TTL. However, it does not state when not to use or provide alternatives, which would strengthen the score.

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