Db Summary

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

With no annotations, the description must convey behavior. It mentions 'Quickly' and the use of set_session_db for default database, but does not disclose caching behavior (despite a refresh parameter), potential performance impacts, or what happens with the limit. The description provides only partial behavioral transparency.

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 only two sentences, front-loaded with the primary purpose, and efficiently mentions the related tool for setting the default database. There is zero fluff; every sentence adds value.

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 tool has an output schema (not shown) and three optional parameters. The description covers the core purpose and usage context (default db). It does not mention output format or edge cases, but the presence of an output schema mitigates that need. It is complete for a quick-summary tool.

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 schema fully describes all three parameters (db, limit, refresh) with clear explanations, achieving 100% coverage. The description adds no extra semantic nuance beyond what the schema provides, so the baseline of 3 is appropriate.

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 the tool's purpose: 'Quickly get summary of a database with tables' schema and size information.' This is a specific verb-resource pair that distinguishes it from siblings like top_hot_tables or analyze_query. It explicitly mentions what it provides (schema and size info) making it 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?

The description indicates when to use the tool (for a quick database summary) and references set_session_db to set a default database, which provides context for its usage. However, it does not explicitly mention when not to use it or alternatives for detailed analysis, so it lacks explicit exclusions.

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