get_current_schema

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

The description reveals what information is returned (current schema and allowed schemas) but does not disclose behavioral traits such as read-only status, whether connections are required, side effects, or failure modes. With no annotations available, the description carries the full burden and only partially covers it.

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 directly states the tool's purpose. It is concise, front-loaded, and contains no filler or redundant information.

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?

For a parameterless getter with an output schema available, the description adequately states what will be retrieved. It could be slightly more complete by noting typical use cases or read-only behavior, but no critical invocation information is missing.

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 is no parameter semantics burden on the description. The description's mention of 'current configured database' and 'allowed schemas' adds meaningful context even though the input schema is empty.

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 states a clear action and resource: retrieve the currently configured database's schema and the list of allowed schemas. It is specific enough to convey the tool's core function, though it does not explicitly distinguish itself from sibling tools like list_tables or switch_schema.

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?

No guidance is provided for when to use this tool versus alternatives such as list_tables, switch_schema, or execute_sql. The intended context must be inferred entirely from the tool name and description, with no exclusions or selection criteria stated.

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