List sequences

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

Annotations already declare readOnlyHint=true, so the description's safety profile is clear. The description adds value by detailing the return fields (name, data_type, start_value, etc.) and scoping to a schema. No contradictions with 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: one sentence stating the action followed by a list of return fields. It is front-loaded and contains no extraneous information. Every sentence is necessary.

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's simplicity and the presence of an output schema, the description covers the main purpose and return format. It could mention edge cases (e.g., behavior for non-existent schemas) or permissions, but for a read-only listing tool it is fairly complete.

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 50% (only database parameter has a description in the schema). The description only implicitly references the 'schema' parameter via 'in a schema', adding minimal meaning. It does not elaborate on the schema parameter's format or constraints, nor does it compensate for the missing schema description.

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 in a schema with specific attributes (range, increment, last value). The verb 'list' and resource 'sequences' are precise, and the output format is described. It distinguishes from sibling list_* tools like list_tables or list_indexes by focusing on sequences.

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 obtaining sequence details but does not explicitly state when to use this tool versus alternatives. No exclusions or comparisons to sibling tools are provided. The name and title give context, but explicit guidance is lacking.

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