list_schemas

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

No annotations are provided, so the description carries the full burden. "Lists" implies a non-destructive read and "accessible" implies permission-based filtering of results, which is genuinely useful behavioral context, but nothing is said about how expensive the call is, whether a live connection is required, or how many schemas are typically returned.

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?

A single front-loaded sentence with no filler; the resource and the distinguishing detail (table counts) both land in one clause.

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?

An output schema exists, so return format needn't be explained, and the description cheaply flags one return field anyway. For a zero-parameter listing tool this is close to sufficient; the missing piece is any statement of connection prerequisites in a toolset that includes set_connection.

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 takes zero parameters, so there is nothing for the description to disambiguate beyond what the (empty) schema states. Baseline 4 applies; the mention of table counts adds a small amount of meaning about what the listing includes.

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?

States a specific verb and resource ("Lists accessible schemas") plus a useful qualifier ("in the Oracle database with table counts"). It is clearly distinguishable from list_tables, but it never names that sibling, so differentiation is achieved only by reading the resource noun.

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 call this versus list_tables or describe_table, and no mention of a prerequisite connection (set_connection exists as a sibling). The only hint is the word "accessible," which describes filtering, not invocation timing.

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