search_collections

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

No annotations are provided, so the description carries the full burden for disclosing behavioral traits. It only says 'Search' and mentions optional query/configuration, without describing read-only nature, return format, pagination, or effects of the config option. This is a minimal, non-disclosing description.

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 a single concise sentence with no filler words, making it easy to parse. However, the term 'configuration' is vague and the description is borderline under-specified, so it is concise but not perfectly crafted.

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?

With no output schema and no annotations, the description needed to explain return values and broader behavior, but it does not. It only states the basic search capability and optional parameters, leaving significant contextual gaps for a tool with a nested config object.

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 description coverage is 100%, with both 'query' and 'config' described in the schema. The description adds no additional meaning beyond restating 'optional query and configuration', so the baseline of 3 applies.

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 uses the specific verb 'Search' with the resource 'all collections in mem.ai', making the core purpose clear. However, it does not explicitly distinguish this from sibling tools like list_collections or search_notes, so it is clear but not fully differentiating.

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 gives no guidance on when to use this tool versus alternatives. It only states what the tool does and mentions optional inputs, with no exclusions, prerequisites, or comparison to sibling tools like search_notes or list_collections.

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