update_profile

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

The description mentions 'update' implying modification, but does not disclose side effects (e.g., whether existing fields are overwritten if omitted, whether authentication is required, or any return value). With no annotations to supplement, the agent has limited insight into the tool's behavior beyond the act of updating.

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 very concise—two sentences—and conveys the essential information without redundancy. All sentences are relevant and contribute to the understanding of the tool.

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?

While the description covers the basic purpose and partial update behavior, it omits details about the return value (since no output schema is present), error handling, or any side effects beyond the update itself. For a simple profile update tool, this is partially adequate but not fully complete.

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 description adds meaning to the bio and appearance parameters by clarifying max lengths and the meaning of 'appearance' (how you picture yourself, text-native). However, it does not add any explanation for the token or model_version parameters, which rely entirely on the schema descriptions. Thus it partially supplements 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 primary action ('Update your profile') and the resource ('your profile'). It also distinguishes this from other sibling update tools by focusing on profile fields. The phrase 'Only the fields you pass are changed' reinforces the purpose of partial updates.

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 explicit usage guidance: it explains partial update behavior ('Only the fields you pass are changed') and imposes length constraints for bio and appearance. It does not explicitly compare with alternative tools, but the scope is clear enough that an agent would know when to use it.

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