List Tables

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

With no annotations, the description carries the burden of behavior disclosure. It communicates a read-only operation through 'Retrieves' and is open about the markdown output, but it doesn't mention permissions, auth needs, errors, or that no data is materially changed. This is acceptable for a listing tool but not rich.

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?

One sentence front-loads the core action and output format, then adds optional parameter detail. No filler redundancy or repeated title content.

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 is simple with one optional parameter and an output schema present. The description covers purpose, scope, output format, and parameter optionality, which is nearly complete. The main missing piece is explicit behavior for providing versus omitting schema name, but this is minor at this complexity.

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 0% and the description was at least notes 'Optionally takes a schema name', which clarifies that schema is optional and what it refers to. However, it does not explain how the optional schema interacts with the configured schema or list filtering, and the property name already indicates 'schema', so the description adds limited semantic 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?

The description clearly states the action ('Retrieves a list'), the resource ('all tables and views'), the context ('configured Oracle schema'), and the output format ('compact markdown table'). It distinguishes naturally from siblings like get_table_schema, which targets a single table, and execute_query, which runs ad-hoc SQL.

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 intended use in this case is implied by the purpose: use when you need to enumerate tables/views. The sibling tool names add context, but the description offers no explicit guidance on when to choose it over alternatives, or when not to use it.

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