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

destructiveHint=true is already declared, but the description goes further by explaining the partial-update semantics ('only the fields you pass change') and the destructive consequence ('previous values are overwritten') plus a recovery path. It does not mention permission or rate-limit requirements, so it is short of exhaustive.

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?

Front-loaded with the WRITE marker and the resource, then the overwrite caveat, then the id source. Only the trailing 'Breeze: GET /api/people/update.' line is of marginal value to an agent choosing a tool, and it reads oddly for a write endpoint.

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 two-parameter mutation with no output schema, the description covers what changes, what is destroyed, and where dependent ids come from, which is most of what an agent needs. It stops short of stating required permissions or whether the response confirms which fields were applied.

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 100%, so the nested field structure, field_type values, details shapes, and id patterns are already documented. The description's note that field_id and option ids come from breeze_list_profile_fields is genuinely useful sourcing context but does not add syntax beyond 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?

States a specific verb ('set profile fields') on a specific resource ('an existing person') and enumerates the field families affected. The 'existing person' framing cleanly separates it from breeze_add_person, and the WRITE prefix makes the mutation nature unmistakable.

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?

Gives an explicit conditional: read values first with breeze_get_person if you may need to restore them. Also routes the agent to breeze_list_profile_fields for field_id and option ids, so the prerequisite chain for a successful call is fully spelled out.

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