Fetch database presets

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

The description states it 'Returns' data, indicating a read operation. However, the annotations include readOnlyHint=false, which contradicts this by suggesting the tool may not be read-only. This is a clear contradiction, and the description does not provide additional behavioral context beyond the annotation.

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 sentence with no unnecessary words. It is front-loaded and concise, every word adds value.

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 tool with no parameters and no output schema, the description sufficiently conveys that it returns a list of available presets for database creation. However, it could mention that the output is a list or provide return format details, but given the simplicity, it is largely 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?

There are no parameters, and schema description coverage is 100%. The description adds no meaning beyond the schema since there are no parameters to describe. Baseline 3 is appropriate.

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 that the tool 'Returns the list of available preset configurations for creating databases'. The verb 'Returns' and resource 'preset configurations' are specific, and the context distinguishes it from sibling tools like create_database or vcs tools.

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 it should be used before creating a database to fetch presets, but does not explicitly state when to use it versus alternatives like get_allowed_presets. No when-not or exclusion criteria are provided.

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