save_context

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

The description discloses a key behavioral trait: it will overwrite a file with the same name. However, with no annotations provided, it lacks details about authentication needs, rate limits, or other side effects. The overwrite disclosure is useful but not comprehensive.

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 concise (two short sentences) and front-loads the action. It efficiently conveys the main purpose and usage context without unnecessary words.

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 5 parameters with no schema descriptions or annotations, the description is insufficient. It does not explain the output schema (though one exists) or cover parameter semantics. The tool's complexity demands more detail for an agent to use it correctly.

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 coverage is 0%, so the description must explain parameters. It does not describe any of the five parameters (slug, title, body, tags, tier). The mention of 'section' is vague and does not map to parameter meanings. This leaves the agent with no guidance on how to fill parameters.

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 action: 'write or update a section' and mentions overwriting, which is specific. It also provides a usage scenario ('after parsing resume/organizing experience'), distinguishing it from sibling tools like list_context, get_context, and search_context which are read-only.

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 gives a clear context for use ('after parsing resume/organizing experience, store the result into the knowledge base'), but it does not explicitly state when not to use or mention alternatives. However, the purpose is clear enough that an agent can infer appropriate usage relative to siblings.

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