memcp_load_context

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

No annotations are provided, so the description carries full burden. It only states basic storage functionality without disclosing behavior such as overwrite policy, error handling, or storage limits. This minimal disclosure leaves significant uncertainty.

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?

Description is short and front-loaded with the main purpose, followed by an Args section. Every sentence adds value, though the name mismatch could be clarified further.

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 4 parameters, no annotations, and an output schema (which covers return values), the description provides adequate usage details. However, it omits error conditions, return value meaning, and how this tool relates to retrieval tools like memcp_get_context.

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 has 0% coverage, so description adds vital meaning: explains name format, content vs file_path exclusivity, and project's optionality. This goes well beyond the bare schema names, making parameter usage clear.

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 it stores content as a named context variable on disk. It distinguishes from sibling tools by specifying its use for large content that should be accessible without loading into the prompt. However, the tool name 'load_context' might imply retrieval, which could cause confusion.

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?

Provides explicit guidance: 'Use this to save large content...' and advises on parameter exclusivity (content OR file_path). Lacks explicit when-not-to-use or alternative tools, but the context is clear enough for an AI agent to decide.

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