search_docsKeyword-search Mitosis documentation and product pages. Returns ranked results with URLs. Use to answer any "how do I…" question about Mitosis.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 5, max 20) | |
| query | Yes | Search terms, e.g. "connect google workspace" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that results are ranked and include URLs, consistent with annotations. No contradictions. Adds useful behavioral detail beyond 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?
Two sentences: first explains function, second advises usage. No unnecessary words. Efficient and front-loaded.
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 simple search tool with rich annotations, the description covers purpose, behavior, and usage. Missing explicit mention of pagination or error handling, but sufficient for typical use.
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% - both parameters (query, limit) are described. The description's mention of 'keyword-search' and example for query ('connect google workspace') adds marginal value beyond the schema. Baseline of 3 is appropriate.
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 'Keyword-search Mitosis documentation and product pages. Returns ranked results with URLs.' This gives a specific verb, resource, and outcome. It distinguishes from siblings like get_platform_status or get_pricing by noting its use for 'how do I…' questions.
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 explicitly says 'Use to answer any 'how do I…' question about Mitosis,' providing clear guidance on when to use. However, it does not mention when not to use or alternatives, which is acceptable given distinct siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
There is significant overlap between cortex_ask, cortex_recall, and search, all of which retrieve from the user's memory. cortex_recall explicitly describes itself as a subset of cortex_ask, and search's description is nearly identical to cortex_ask's core function, making it hard for an agent to choose correctly. Other tools are more distinct, but this triple overlap creates real ambiguity.
The naming is inconsistent: memory tools are split between a cortex_* prefix (ask, recall, manifest, status, etc.) and bare fetch/search, with no clear rule for which gets the prefix. Within cortex_*, some are verbs (ask, recall, remember) and some are nouns (manifest, status, connectable_sources), and platform tools use get_/list_/search_ prefixes, resulting in a mixed and unpredictable naming pattern.
13 tools is a reasonable number for a server covering both memory operations and platform information. However, the presence of three overlapping retrieval tools (cortex_ask, cortex_recall, search) slightly inflates the count, suggesting some redundancy rather than each tool earning a unique place.
The server covers core workflows: reading memory (ask, search, recall, fetch, manifest), writing memory (remember, ingest_conversation), checking health (status), and accessing platform info (get_platform_status, get_pricing, list_skills, search_docs). Minor gaps include no explicit update/delete for individual memories and no direct tool to connect new sources (only listings of connectable ones), but these are often user-driven actions.