nex_account_modify

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that password and 2FA secret are write-only and never returned, and that updates are partial, but it does not explain permissions, reversibility, side effects, or overall return behavior for a mutation tool.

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 three short sentences, front-loaded with the core operation and followed by key usage and secret-handling constraints. There is no filler.

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 mutation tool with no annotations and no output schema, the description covers partial updates and write-only secrets but omits important call context such as the required account identifier, return behavior, and permission assumptions. It is adequate but incomplete.

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 only 44% across 9 parameters. The description clarifies write-only handling for password and 2FA secret but does not explain other parameters such as username, platformUrl, platformName, remark, or teamId, nor does it add much beyond the schema's own accountId/id notes.

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 and resource: "Update one platform account in the workspace catalog." It clearly identifies the operation and scope, though it does not explicitly distinguish itself from sibling tools such as nex_account_create, nex_account_delete, or nex_account_batch_create.

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 phrase "Pass only the fields that must change" gives useful partial-update guidance, but there is no explicit when-to-use or when-not-to-use guidance relative to create/delete/list/batch siblings. Usage is implied rather than fully directed.

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