get_schema_overview

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention that this is a read-only operation, how large the response might be, or whether any filtering or formatting applies. The description merely lists content items without behavioral context.

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 a single short sentence that is entirely front-loaded with the key information. It contains no unnecessary words, making it appropriately concise for a simple tool.

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 present, so the description should explain the return format, but it does not. The fragment 'Tables, columns, PKs, FKs' is ambiguous about whether the output is a list, a nested object, or a formatted report, leaving gaps for an agent.

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 tool has zero parameters, so there are no parameter semantics to clarify. The description's content listing (tables, columns, PKs, FKs) aligns with what an overview would provide, satisfying the baseline for a parameter-less tool.

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 provides schema metadata including tables, columns, primary keys, and foreign keys for the connected database. It is specific about the content scope, though it lacks an explicit verb; the tool name 'get_schema_overview' supplies that. It doesn't explicitly contrast with sibling tools, but the content is distinct from analytical siblings.

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?

There is no guidance on when to use this tool versus alternatives like find_missing_indexes or generate_erd. The description only declares what the tool returns, not when it should be invoked or what scenarios it addresses.

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