expand_search

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

The description reveals no behavioral aspects such as side effects, permissions, or whether the operation is read-only. Since no annotations are provided, the description carries full responsibility for transparency and fails to offer any.

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 extremely brief, which is concise but it sacrifices clarity. The phrasing is cryptic and lacks structure, making it difficult to parse the intended meaning.

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?

The description is incomplete given the ambiguity. It fails to provide a clear overview of the tool's capabilities, parameters, or relationship to sibling tools, leaving significant gaps in understanding.

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 schema parameters 'query' and 'k' are not explained in the description. There is no indication of what each parameter does, how they influence the search, or their expected formats.

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 'search_vault + wikilinks discovered in source files' is vague and does not clearly state the tool's primary function. It hints at combining search with wikilinks but lacks a specific verb like 'searches' or 'expands'.

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 is provided on when to use this tool versus the sibling tools 'search_vault' or 'related_notes'. The description gives no context for appropriate usage scenarios.

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