List PostgreSQL Sequences

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by detailing the return format (JSON/Markdown with specific columns) and a critical behavioral note: 'last_value reflects the last allocated value, not necessarily the next one to be issued.' This provides clarity beyond annotations.

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 concise with two clearly separated paragraphs (purposes and return format/note). Every sentence adds value, and the most critical information is front-loaded in the first sentence.

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?

For a simple listing tool with no output schema, the description adequately covers the return structure (JSON/Markdown with specific columns) and the important last_value nuance. However, it lacks details on error handling or behavior when the schema does not exist, which would make it more robust.

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% with both parameters (schema, response_format) fully described in the input schema. The description restates them in the Args section but adds no additional semantics or constraints beyond what the schema already provides.

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 'List all sequences in a schema with their configuration and current state.' It uses a specific verb+resource combination and distinguishes the tool from siblings like pg_list_tables or pg_list_indexes.

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 listing sequences but does not explicitly mention when to use this tool versus alternatives or provide exclusion criteria. The note about last_value is a usage nuance but does not serve as a guideline.

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