update_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 that the tool performs a partial update (not a full replace), and importantly that it may create a profile if none exists and profile_id is omitted. This gives useful behavioral context beyond the schema. However, it lacks details about validation, error behavior, or auth requirements, so it is not fully transparent.

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?

Two concise sentences that front-load the primary action and add the critical conditional behavior. No wasted 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 the tool's simplicity (2 params, output schema present), the description covers the core behavior and the key profile_id nuance. It could be improved by noting what happens for invalid profile_id or empty patch, but overall it is sufficient for an agent to select and invoke 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 description coverage is 0%, so the description must explain parameters. It clarifies the behavior and semantics of profile_id (optional, defaults to active profile, can trigger creation). However, it does not explain the structure or allowed keys of the patch object beyond implying a partial update, so the parameter semantics are only partially covered.

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 tool's action ('Apply a partial update') and the resource (profile). It also explains the behavior when profile_id is omitted, distinguishing it from create_profile (which explicitly creates) and set_active_profile (which sets active). This provides a specific verb+resource+scope.

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 clear context for when to omit profile_id (to update active profile or trigger creation on the setup path). It implies the tool is for partial updates rather than full creation, but it does not explicitly exclude alternatives like create_profile for new profiles. This is clear context but lacks explicit when-not guidance.

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