ContextStream MCP Server

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

Annotations provide clear safety information (readOnlyHint=true, destructiveHint=false, idempotentHint=true), so the description doesn't need to repeat these. However, the description adds no behavioral context beyond what's in annotations - no information about rate limits, authentication needs, or operational constraints. It merely lists actions without explaining their behavior or consequences.

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 dense, unstructured list of 48 action names organized into 8 categories. While it attempts categorization, it's not front-loaded with purpose, lacks clear structure, and contains excessive detail that belongs in documentation rather than a tool description. Every sentence doesn't earn its place as most are just action enumerations.

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 complex tool with 45 parameters, no output schema, and rich annotations, the description is inadequate. It fails to explain what the tool actually does, when to use it, or how actions relate to each other. While annotations cover safety aspects, the description doesn't provide the contextual understanding needed for an agent to effectively select and invoke this multifaceted tool.

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 100% schema description coverage, the input schema comprehensively documents all 45 parameters. The description adds minimal value by grouping actions into categories (Event actions, Node actions, etc.), but provides no additional semantic context about parameter usage, relationships, or constraints beyond what's already in the schema.

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 lists action categories but doesn't state what the tool actually does. It's essentially a catalog of available actions rather than explaining the tool's purpose. While it mentions 'Memory operations for events and nodes,' this is vague and doesn't distinguish this tool from potential siblings like 'context' or 'project' that might also handle memory-related operations.

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?

There are no usage guidelines whatsoever. The description doesn't indicate when to use this tool versus alternatives like 'context' or 'project,' nor does it provide any context about appropriate use cases. It's purely a list of available actions without guidance on selection or application.

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