derivation_search_saved

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

With no annotations, the description carries the full burden. It clearly indicates a read-only search operation and provides a return format example. It does not disclose limitations like pagination or sort order, but these are relatively minor for a simple search tool.

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 structured with purpose, Args, Returns, and Example, conveying all necessary information in a compact, easy-to-parse format. Every section adds value.

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 single-parameter search tool with no annotations, the description covers the operation, the parameter, the result shape, and an example. It is complete enough for an agent to select and invoke correctly, especially given an output schema exists.

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 provides only type and required flag for 'query', but the description adds the semantic meaning '搜尋關鍵字' (search keyword), fully clarifying the parameter's purpose. This compensates for the 0% schema coverage.

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 saved derivation results by keyword across name, description, and tags, using a specific verb '搜尋' and resource. This distinguishes it from sibling tools like derivation_list_saved (which lists all saved) and formula_search.

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 clear context on what is searched (name, description, tags), giving the agent an understanding of when to use it. However, it does not explicitly name alternatives or provide exclusions, so a small deduction is made.

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