search

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

Describes the hybrid search algorithm, output format (ranked results, relevance scores, excerpts, citations), and includes note about pre-formatted citations. No annotations provided, so it carries full burden. Could be improved by explicitly stating it is read-only and has no side effects.

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?

Two concise sentences with front-loaded core function. Every word adds value; no redundancy.

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 complexity of a search tool with filters and an output schema, the description adequately covers purpose and output but could mention default behavior of searching all collections when no collection specified (though schema covers it). Overall sufficient.

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 description need not add much. It does not elaborate on parameters beyond what the schema already provides, giving no extra meaning.

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?

Description clearly specifies the action (Search), the resource (Point's verified knowledge base), and the method (hybrid search). It distinguishes itself from sibling tools like get_document_full which focus on retrieving documents rather than searching.

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 on when to use this tool versus sibling tools. The description does not provide usage context or alternatives, leaving the agent to infer usage from tool names.

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