search_clickhouse

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions that the tool is 'currently unimplemented', which is confusing but doesn't describe actual behavior like error handling, performance characteristics, or what happens when queries are executed. No useful behavioral context is provided.

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?

While brief, the description is poorly structured and confusing. The 'currently unimplemented' note undermines the tool's purpose without explanation, making it inefficient. It fails to front-load useful information about what the tool actually does.

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 database query tool with 3 parameters and no annotations or output schema, the description is incomplete. It doesn't explain what the tool returns, how results are formatted, or any limitations. The 'unimplemented' note creates ambiguity rather than providing necessary context.

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 100%, so the schema already documents all three parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema, maintaining the baseline score of 3.

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 states the tool's purpose as 'Query Clickhouse database', which is clear but vague. It doesn't specify what kind of queries are supported or what resources are accessed. The 'currently unimplemented' note adds confusion rather than clarifying the actual functionality.

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?

No guidance is provided on when to use this tool versus the sibling tools (search_cloudbeds_pms, search_logs). The description doesn't mention any prerequisites, alternatives, or specific contexts where this tool would be appropriate.

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