mnemos_context

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

The description claims 'assemble context', implying a benign read operation, but annotations indicate destructiveHint=true. The description fails to disclose that this tool may alter or delete state, creating a misleading impression.

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 that front-loads the primary action. It is appropriately sized for a simple tool, though it could include a bit more context without becoming verbose.

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 4 parameters, the description is too sparse. It does not explain what 'context' means, how relations are included, or what the return format is. The behavior around token budget and destructive side effects is not elaborated.

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 parameters are already well-documented. The description adds no new semantic information beyond echoing 'query' and 'token budget'. Baseline score 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 verb 'assemble' and resource 'relevant context', which clearly indicates the tool's purpose is to compile context for a query. It distinguishes from siblings like mnemos_search (which likely searches for specific items) and mnemos_store (which saves), but does not explicitly contrast them.

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 mnemos_search or mnemos_get. The description does not mention prerequisites or conditions under which this tool is preferred.

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