list_brainstorm_sessionsRetrieve recent brainstorm sessions with title, turn count, and status to review or resume prior ideation work. Set a limit to control how many sessions are returned.
List recent brainstorm sessions with title, turn count, and status.
Args:
limit: Maximum sessions to return (default 20).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not state whether the tool is read-only, has side effects, or any behavioral constraints. Minimal information beyond the basic listing action.
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?
Extremely concise: two sentences plus parameter doc. No wasted words, front-loaded with purpose.
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 list tool with an output schema, the description adequately covers the return fields and parameter. Could mention what 'recent' means or edge cases (e.g., empty list), but overall sufficient.
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?
With 0% schema description coverage, the description compensates by explaining the 'limit' parameter (maximum sessions, default 20). This adds meaningful context beyond the schema's type/default.
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 verb 'List' and the resource 'brainstorm sessions', and specifies the fields returned (title, turn count, status). It distinguishes from siblings like 'get_brainstorm_session' but doesn't explicitly differentiate from 'list_recent_sessions'.
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?
No guidance on when to use this tool versus alternatives like 'list_recent_sessions' or 'get_brainstorm_session'. Lacks context on prerequisites or filtering scope.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.