describe_schema

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

The description mentions a 'refresh=true' parameter, but the input schema has no parameters defined. This contradicts the schema, misleading the agent about available options. Additionally, no annotations are provided to clarify behavior.

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?

Extremely concise—two sentences convey purpose, caching, and usage tip with 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?

No output schema is provided, and the description does not explain the return format or structure of the schema data. While it lists what is included, this is insufficient for a tool with no output schema and no annotations.

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 100% (no parameters), so baseline is 3. However, the description invokes a non-existent parameter ('refresh=true'), adding confusion instead of value.

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 the tool discovers the full database schema and enumerates its components (tables, columns, types, primary keys, foreign keys, indexes). Differentiates itself from siblings like 'analyze_table' or 'query_sql' which are more about querying or analyzing specific data.

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?

Provides guidance on caching behavior (results cached 1 hour) and suggests using 'refresh=true' after schema changes. However, it does not explicitly state when not to use this tool or compare it to alternatives among the many siblings, leaving some ambiguity.

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