segnals_search_knowledge

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

The description discloses that the tool uses semantic search and is coming soon with the endpoint not yet available. This is important behavioral disclosure beyond the operation. Since no annotations are provided, the description carries the full burden and does so effectively. It also notes the required scope, but does not detail rate limits or output format.

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 concise, consisting of three sentences that are front-loaded with the purpose, followed by behavioral notes and an example. Every sentence adds value, with no unnecessary 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?

Given the tool has only one parameter, no output schema, and no annotations, the description covers the purpose, behavior, usage example, and availability warning. It does not describe the return format, but for a simple search tool, this is a minor gap. Overall, it is fairly complete for an agent to understand and invoke the tool correctly.

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 input schema has 100% coverage for the single parameter 'query' with a description. The tool description adds an example call demonstrating usage, which provides context beyond the schema. No additional details on query format or constraints are given, but the combination is sufficient.

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 searches the Segnals knowledge base for help articles, feature documentation, and trading guides using semantic search. It specifies the resource (knowledge base) and action (search), distinguishing it from sibling tools like segnals_get_news or segnals_get_capabilities.

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 provides an example query and mentions that the tool uses semantic search, implying its use for finding relevant content. However, it does not explicitly state when to use this tool versus alternatives or when not to use it. Given the absence of a direct sibling search tool, the guidance is clear enough 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.