store_search_all

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

The description adds behavioral details beyond the annotations: it explains the _collection field in each hit and the pagination mechanism with next_cursor. It also clarifies the read-only nature, consistent with readOnlyHint, and does not contradict any annotations.

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 concise but includes a slight redundancy in 'across every SOIL collection you can see — all of them, or only your manifest's store_scope if one is set.' It is well-structured with clear separation of scope, output, and pagination details.

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?

While the core purpose and pagination are covered, the description omits any explanation of required parameters like app_id and query. This makes the description incomplete for an agent to correctly invoke the tool without additional context.

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 description does not explain any of the four parameters (app_id, query, limit, cursor). Since schema description coverage is 0% and the description does not compensate, it adds no value to parameter understanding.

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 clear distinction from store_search. It also notes the optional store_scope restriction, 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?

Explicitly instructs to use this tool when the target collection is unknown and to prefer store_search otherwise. This provides a direct usage guideline and differentiates from the sibling tool.

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