get_postgis_diagnostics

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

No annotations are provided, and the description does not indicate whether the tool is read-only, destructive, or requires specific permissions. The term 'bounded' is ambiguous and unexplained, leaving behavioral traits unclear.

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, concise sentence that immediately states the tool's purpose. There is no redundant or unnecessary information; every word contributes to clarity.

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 two parameters with schema descriptions and no output schema, the description provides minimal context. It does not explain what 'bounded' means, what the output contains, or any usage considerations. For a diagnostic tool, more context is needed for effective decision-making.

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 100%, so the baseline is 3. The description does not add additional meaning beyond the schema, which already describes max_columns and max_indexes with defaults and constraints. The phrase 'bounded' loosely relates but adds no specific param insight.

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 ('Report') and resource ('bounded PostGIS columns and indexes'), and specifies the method ('through PostgreSQL core catalogs'). It effectively differentiates from sibling tools like get_pgvector_diagnostics by focusing on PostGIS.

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 like get_pgvector_diagnostics, get_runtime_metrics, or other diagnostic tools. No context on prerequisites or intended scenarios.

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