hac_flexsearch

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

No annotations are provided, so the description carries the full burden, yet it discloses no behavioral traits: whether FlexibleSearch is read-only, whether writes are possible, whether permissions or SSO are required, or how result limits behave. It only restates the operation itself.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly a symptom of missing content rather than disciplined editing.

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?

An output schema exists, so return values need not be explained, but the description still leaves critical gaps: no annotations, no parameter documentation, no usage guidance for a query-execution tool that could otherwise be confused with hac_groovy_execute. It is under-specified for a 3-parameter, potentially powerful 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?

Schema description coverage is 0%, so all three parameters (host, query, max_count) are undocumented in structured data. The description only obliquely implies that 'query' holds FlexibleSearch syntax; it says nothing about host defaults or what max_count controls.

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 gives a specific verb (Executes) and resource (a FlexibleSearch SQL query against the SAP Commerce database), so an agent knows exactly what the tool does. It does not, however, distinguish this from adjacent siblings such as hac_groovy_execute, which could plausibly also run queries or arbitrary code.

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?

There is no statement of when to use this tool versus alternatives (e.g. hac_groovy_execute, hac_impex_import), no prerequisites, and no mention of host selection or environment targeting. Usage context is left entirely to inference from the name.

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