set_profile

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

Details partial update behavior, field constraints (4-digit years, currency conversion to USD, enum values), and free-form notes. No annotations are present, so the description carries the burden; it adequately discloses key behaviors without contradiction.

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 sentences: first states purpose and partial update, second lists field constraints. Every sentence adds value; no fluff. Front-loaded with core purpose.

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 simple update tool with 6 optional parameters and no output schema, the description covers the essential behavior, field formatting, and currency conversion. No critical gaps remain.

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?

Adds significant meaning beyond the schema: explains 4-digit years for birth_year and retirement_target_year, currency conversion for target_net_worth, enum values for risk_tolerance, and free-form for notes. Schema coverage is only 33%, but description compensates fully.

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 starts with 'Update the user's profile,' clearly stating the verb and resource. It specifies partial updates, distinguishing it from sibling tools like 'show_profile' (read) and others.

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?

Explicitly says 'Partial updates — only provided fields are changed' and 'All fields are optional; capture only what the user volunteers, never invent values.' Provides clear context but does not explicitly mention when not to use or alternative tools.

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