get_from_user_custom_where

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adds value by clarifying the filtering behavior ('flexible filtering with structured JSON conditions'). However, it does not disclose details like whether conditions support complex operators or what happens when no rows match.

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 of 12 words, front-loading the key information. It is concise without wasted words.

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 2-parameter read-only tool with good annotations, the description is adequate but lacks details on return format, error handling, or empty results. With nested objects, additional context on the conditions structure would be helpful.

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 coverage is 100% (both parameters documented), so baseline is 3. The description mentions 'structured JSON conditions' but does not go beyond the schema to explain the format or allowed operators for the 'conditions' object.

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 performs 'Flexible filtering' on 'user_directives.db tables' using 'structured JSON conditions'. It uses the verb 'get' and specifies the resource (user_directives.db), distinguishing it from sibling tools like 'get_from_user_custom' which likely returns all rows.

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 filtered queries but does not explicitly state when to use this tool over alternatives like 'get_from_user_custom' or 'query_user_custom'. It lacks guidance on exclusions or prerequisites.

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