List Tables

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

No annotations are provided, so the description carries the burden. It usefully discloses a non-obvious default behavior (returns all OpenCart tables using the detected prefix), which is real added value. However it omits whether this is read-only (implied), permissions required, and how results are ordered or capped.

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?

Two short sentences, front-loaded with the action and immediately followed by the default scoping behavior. Zero filler.

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 values need not be described. But for a listing tool with an undocumented filter parameter and no sibling routing, the description leaves the pattern format and the read-only/prefix assumptions partly unresolved.

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 single 'pattern' parameter is documented only as 'matching pattern'. No syntax is given — LIKE wildcards, regex, or glob — so an agent cannot construct a valid filter without guessing. The description gestures at the parameter without compensating for the schema gap.

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+resource ('List database tables') plus a scoping mechanism (pattern matching). It is distinguishable from siblings like get_table_schema and query, though it doesn't explicitly name them. Clear but not maximally differentiated.

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 on when to use this versus get_table_schema, query, or run_sql, all of which touch the same database. The 'Default: all OpenCart tables' note hints at a use case but never states when/when-not to call it. An agent must infer the routing.

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