list_available_query

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action 'list' which implies read-only, but it does not explicitly mention side effects, authentication requirements, or rate limits. For a listing tool, the behavior is minimally transparent but lacks explicit safety guarantees.

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 two sentences long, with the main action front-loaded. The second sentence explains the purpose of query builders, adding value without unnecessary fluff. Every sentence earns its place.

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?

The tool is simple (0 params, output schema exists), and the description sufficiently explains what it does and the context of query builders. It does not need to detail return values because an output schema is present. However, the description could briefly mention that it is a safe read-only operation.

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?

The tool has 0 parameters, and since there are no parameters to document, the description does not need to add parameter semantics. The baseline for 0 params is 4, and the description does not need to compensate for any missing parameter info.

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 'List all available clearskies query builder types' with a specific verb ('list') and resource ('query builder types'), and it provides a short description of each. This distinguishes it from sibling list tools like list_available_backends or list_available_columns.

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 gives clear context about what query builders are ('used to construct database queries programmatically'), which implies when to use this tool. It does not explicitly mention alternatives or exclusions, but the extra sentence provides enough usage context for an AI agent.

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