find_related_context

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

Discloses vector search method, sub-second speed, and condition when no results are returned (embeddings not built). With no annotations, description carries full burden and provides useful behavioral context, though could detail output format further.

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?

Well-structured with clear sections. Every sentence adds value. Front-loaded with purpose, followed by usage, behavior, and parameter details. No 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 multi-source semantic search tool with two parameters and an output schema, the description covers purpose, usage, behavioral nuances, and parameter details comprehensively. Output schema exists, so return value details are not required.

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?

Adds crucial meaning beyond schema: query is free-text, required, non-empty; limit range 1-50, default 10. Schema coverage 0% so description fully compensates with clear parameter semantics.

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?

Clearly states it finds semantically related screen, voice, and clipboard entries. Provides a unified list with ranking and source-type tags. Distinguishes from single-source siblings.

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?

Explicitly specifies USE WHEN for open-ended recall across multiple data types and NOT FOR single-source search, naming alternatives (search_history, search_voice, search_clipboard).

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