ContextStream MCP Server

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, covering basic safety and idempotency. The description adds context about specific actions (like indexing, audit trails, local folder ingestion) that suggest behavioral traits beyond annotations, such as file system operations and team-specific features. However, it doesn't disclose important behavioral details like rate limits, authentication needs, or side effects of actions like 'ingest_local' or 'index'.

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 run-on sentence listing 12 actions without proper structure or prioritization. It's front-loaded with 'Project management' but then devolves into a dense, comma-separated list that's hard to parse. While concise in word count, it lacks readability and fails to organize information effectively for quick comprehension.

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?

Given the tool's complexity (20 parameters, 12 actions) and rich annotations, the description is moderately complete. It identifies all actions but lacks output details (no output schema) and doesn't explain relationships between actions and parameters. For a multi-action tool with no output schema, more guidance on expected results or error conditions would improve completeness, but the action list provides a basic operational map.

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%, so the schema fully documents all 20 parameters. The description mentions actions that correlate with parameters (e.g., 'ingest_local' relates to 'folder_path', 'path'), but adds no additional semantic meaning beyond what's in the schema. This meets the baseline of 3 when schema coverage is high, as the description doesn't compensate with extra parameter insights.

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 states 'Project management' and lists 12 specific actions, which clarifies the tool's domain and available operations. However, it doesn't provide a clear verb+resource statement (like 'Manage projects by performing operations such as...') and doesn't distinguish this tool from potential siblings beyond the generic domain name. The action list is helpful but presented as a bullet rather than integrated into a purpose statement.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention any of the sibling tools (context, generate_rules, graph, etc.) or explain which project-related operations belong here versus elsewhere. The agent must infer usage solely from the action list without any contextual boundaries or exclusions.

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