Pg Tables

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 only states the output content (tables with sizes and statistics) but does not disclose whether the operation is read-only, any permission requirements, or performance implications.

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 extremely concise and front-loaded, but it is under-specified rather than efficiently complete. It fits in one sentence but omits essential guidance, making it acceptable yet minimal.

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?

Given the tool has a generic parameter object and no annotations, the description should compensate with usage context and parameter guidance. It does not, leaving agents without enough information to know how to invoke it correctly beyond calling with default null parameters. The presence of an output schema helps return-value understanding but not invocation semantics.

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 description coverage is 0%; the only parameter is a generic 'params' object with no documented properties. The description does not mention parameters at all, so it adds no meaning beyond the input schema.

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 a specific verb and resource: listing tables with their sizes and statistics. This distinguishes the tool from siblings like pg_connections or pg_replication, though it doesn't explicitly name alternatives.

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 description provides no guidance on when to use this tool versus alternatives such as pg_stats or pg_activity. There are no usage contexts, exclusions, or mentions of prerequisites.

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