save_profile

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It specifies that the current config is snapshotted, but it does not explain the behavior when the profile already exists with overwrite=false or other potential side effects like file permissions.

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 sentence that is directly front-loaded with the action and purpose. No redundant or extraneous information is present.

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?

The description effectively conveys the primary effect of the tool. However, since there is no output schema, the agent is not informed about what the tool returns (e.g., a success status or profile name), which would be helpful for confirmation.

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?

The input schema has 100% coverage, so the baseline is 3. The description adds context for the 'name' parameter by indicating it labels the profile, but it does not mention the 'overwrite' parameter, so no additional value beyond 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 clearly states the action ('Snapshot') and the resource ('current ~/.claude.json') and the outcome ('as a named profile'). It distinguishes itself from sibling 'switch_profile' by specifying the restore functionality elsewhere.

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 clear context by explaining when to use the tool (to save a profile for later restoration via switch_profile). However, it does not explicitly state when not to use it or mention alternatives beyond switch_profile.

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