store_search_all

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

With no annotations provided, the description carries the safety burden. It discloses the tool is read-only, describes the token-AND matching behavior, and notes the _collection field in each hit. It does not mention pagination or limits, but for a search tool this is sufficient for a high score.

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?

Three sentences, no filler. The core action is front-loaded, each sentence adds value (scope, output field, usage guidance, safety), and it achieves maximum information density without bloat.

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?

Lacks an output schema, but the description partially compensates by mentioning the _collection field. It covers scope, usage, and safety. The missing parameter explanation and absence of any response structure description prevent a perfect score, but overall it is reasonably complete for a focused search tool.

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 coverage is 0%, so the description must explain parameters. It does not clarify that 'query' contains search tokens or what 'app_id' represents. The mention of 'Token-AND' hints at query semantics, but neither parameter is explicitly documented, which is a significant gap.

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 performs a token-AND search across all visible SOIL collections, with a specific scope conditional. It explicitly distinguishes from sibling tool store_search by advising when to use each, making the purpose unambiguous.

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?

Provides explicit usage guidance: 'Use when you don't know which collection holds the data; prefer store_search when you do.' It also explains the manifest store_scope behavior, giving clear context for when this tool is appropriate.

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