set_profile

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

With no annotations, the description carries full burden. It discloses the partial update behavior, optional fields, and field-specific constraints (4-digit years, enum, free-form notes). It does not mention side effects like persistence or immediate visibility, but the mutation nature is clear and honestly described.

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, well-structured sentence with no fluff. It front-loads the core action 'Update the user's profile' followed by concise details on partial updates and field constraints. Every sentence adds value.

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 input fields and constraints well, it omits the return value or success behavior. For an update tool, agents typically need to know if the updated profile is returned or if a simple confirmation is given. This is a notable gap given the lack of an output schema.

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 0%, so description must compensate. It adds meaning for all 5 parameters: birth_year and retirement_target_year are 4-digit years, target_net_worth_usd is USD, risk_tolerance enum values, notes is free-form for preferences. This greatly enhances the schema's minimal type/constraint info.

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 'Update the user's profile' with a specific verb and resource. It distinguishes from sibling tool 'show_profile' by indicating a write operation. Partial updates are explicitly mentioned, and all fields are described with constraints.

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 guidance: 'capture only what the user volunteers, never invent values.' This indicates when to use the tool (when user provides data). However, it does not explicitly mention alternatives or when not to use, though the sibling list implies read operations use 'show_profile'.

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