set_primary_profile

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

With no annotations provided, the description carries the disclosure burden. It discloses the key behavioral side effect (previous primary becomes secondary) and the access restriction that start_login does not open this tool. It does not discuss reversibility, failures, or response shape, but the essential mutation behavior is transparent for a simple one-parameter tool.

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 and front-loads the primary action and side effect. The ACCESS block is terse and slightly unusual with the server-restart instruction, but it contains no filler and every sentence contributes useful information.

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?

For a single-parameter mutation with no output schema, the description covers the action, the side effect, and the access prerequisite. It does not describe return values or error conditions, but the tool is simple enough that these are acceptable gaps.

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 100%, and profile_id is already described as 'Profile ID to set as primary.' The description adds no extra detail about parameter constraints, formatting, or validation, so it stays at the baseline for fully documented schema 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 states the exact action and resource: 'Set a profile as the primary profile.' It also explicitly discloses the side effect that the previous primary profile becomes secondary, clearly distinguishing this from generic profile updates and from sibling primary setters like set_primary_email or set_primary_phone.

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 purpose implies when to use the tool, and the ACCESS note provides a prerequisite (Proof account with PROOF_API_KEY set). However, there is no explicit guidance about when to choose this tool over alternatives such as update_profile or set_primary_email, and no mention of conditions where this tool should not be used.

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