Save user persona

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

Discloses that saving overwrites the relevant part of the merged view and clarifies the project vs global behavior. The idempotentHint annotation is consistent with the overwrite semantics.

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 compact, directly relevant, and front-loads the core action. No redundant or filler wording 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?

Provides enough context for correct invocation, including the critical default-scope behavior and the purpose of the tool. No significant missing details are apparent.

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 already describes content and scope, and the description adds meaningful context about the default scope and its merged-view effect. This goes beyond the basic parameter descriptions without being excessive.

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?

Clearly states the tool saves or overwrites persona markdown, distinguishing it from persona_get. The description also explains the two scopes and their effect, making the purpose unambiguous.

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?

Explains that it defaults to the current project layer and that global writes the base persona, with a stated use case of maintaining the persona or project-specific rules. It does not explicitly contrast with sibling tools, but the context is clear enough for selection.

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