List sequences in a schema

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

Annotations already declare the operation as read-only, idempotent, and non-destructive. The description adds context by specifying the system view source and the exact fields returned, which aids in understanding output shape. It does not mention pagination or ordering details, but safety traits are fully covered by 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 a single, concise sentence that front-loads the action ('List sequences') and includes the key resource and output details. No unnecessary words or repetition.

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 simple nature of a list tool and the presence of annotations, the description provides sufficient information about the tool's purpose and output. It lacks explicit pagination/default behavior, but the parameters limit/offset are self-explanatory and the description covers the core functionality.

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 only 50%, with limit and offset lacking any description. The description does not compensate by explaining parameter behavior, such as the default schema_name or how prefix filtering works. It only lists output fields, leaving undefined parameters without guidance.

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 tool lists sequences from a specific system view (SYS.SEQUENCES) and enumerates the exact attributes shown (start, min, max, increment, cycle, cache). This distinguishes it from sibling listing tools like list_tables or 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 viewing sequence definitions but provides no explicit guidance on when to use this tool over alternatives. It does not mention exclusions or alternative tools, leaving the agent to infer from the tool name and content.

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