find_tables

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

No annotations provided, so description fully carries the burden. Details cache auto-refresh, Snowflake auth requirement, case-insensitive search, and output structure. This goes beyond basic disclosure.

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?

Well-structured with clear sections (USE THIS WHEN, RETURNS, HOW IT WORKS, Parameters, Examples). Every sentence adds value, no fluff. Front-loaded with purpose.

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?

Output schema is present (description shows return structure). For a simple single-parameter search, it covers when to use, how it works, output format, and examples. Complete 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 description coverage is 0%. Description adds meaning: 'Keyword to search for (case-insensitive)' and examples of usage. While helpful, it does not provide extensive detail beyond the schema.

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?

Clearly states 'Search for tables by keyword across ALL databases.' Specific verb-search, resource-table, and scope-all databases. Distinguishes from sibling tools like 'show_tables' (which likely lists tables in a specific database) by emphasizing cross-database search.

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 indicates when to use: 'USE THIS WHEN: You don't know where a table is, but know part of its name or purpose.' Provides examples but does not mention when not to use. However, context from sibling tools and examples compensates.

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