pg_table_stats

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

No annotations exist, so the description carries the full burden. It discloses that the tool is read-only by nature (getting stats) and lists included output fields. However, it does not explicitly state side effects, authentication needs, or that it only reads data. The disclosure is adequate but not explicit.

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, front-loaded sentence that conveys essential information without wasted words. It efficiently communicates the tool's core function.

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 no output schema and a simple tool, the description adequately lists the returned statistics. However, it lacks details on response format, pagination (if any), or error scenarios. For a straightforward read operation, this is sufficient but not comprehensive.

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 67% (schema and connectionId have descriptions, table does not). The description adds value by linking parameters to the tool's purpose ('Get statistics for a given table in the specified schema'), but it does not elaborate on parameter formats or constraints beyond the 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 the verb 'Get' and the resource 'statistics for a given table in the specified schema'. It explicitly lists included statistics (table size, index size, estimated row count), distinguishing it from sibling tools like 'pg_describe_table' or 'pg_list_tables'.

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 implies usage for retrieving table statistics but provides no explicit guidance on when to use this tool versus alternatives like 'pg_sizes_overview' or 'pg_index_usage'. No when-not-to-use or prerequisite info is given.

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