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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the description earns credit for adding genuinely new context: omitted fields are not sent (true partial update, no implicit clearing), the return value is the groupID, and the underlying endpoint is POST groups/update. It stops short of warning that this is a destructive mutation on a shared CRM record or noting whether unintended field wipes are possible.

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?

Three compact clauses with the operation class front-loaded as 'WRITE:', followed by semantics and return 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?

For a destructive, open-world mutation of a nested-object schema with 12 parameters and no output schema, the description covers the essentials (action, partial-update behavior, return value) but leaves out permission requirements, field-level mutability caveats, and any caution appropriate to destructiveHint=true. Adequate but with clear gaps.

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?

With only 42% schema description coverage across 12 parameters, the description does some compensating work by establishing that all non-required fields are optional and omitted ones are simply not transmitted — critical for interpreting this schema. However, it adds no meaning for individual parameters (custom_fields keying, account_manager accepting a user id or name, servicing_agent_id), all of which the schema must carry on its own.

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+resource ('change fields of an existing group') and explicitly scopes it to existing records with partial-update semantics, which cleanly separates it from agencybloc_create_group and the other update_* siblings. The 'including its name' clause also preempts the common question of whether the name is a mutable field.

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?

Usage is implied through the WRITE marker and 'fields you leave out are not sent', which tells the agent how to call it but not when to prefer it over alternatives or what prerequisites (group must exist, correct group_id) apply. No exclusions or cautions are given despite destructiveHint=true.

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