wave_update_account

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

The description is extremely vague, with zero behavioral disclosure. It does not mention whether updates are full replacements or merges, what permissions are needed, or any side effects. No annotations exist to compensate.

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?

While the description is very short, it is under-specified for a tool with 4 parameters, no annotations, and no output schema. Conciseness sacrifices essential information, making it insufficient.

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?

Given that there are 4 parameters, no annotations, and no output schema, the description fails to provide necessary context about success/failure, constraints, or return values. It is not complete enough for an update operation.

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?

The input schema has 100% description coverage, so the description adds no extra value. Per guidelines, the baseline is 3, and no parameter semantics are provided beyond what the schema already states.

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 the action ('Update') and the resource ('existing account'), which distinguishes it from creation or deletion tools. However, it lacks nuance about partial updates or idempotency, which could be inferred from the schema but not stated.

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?

No guidance is provided on when to use this tool versus alternatives like wave_create_account or wave_get_account. There is no mention of prerequisites, context, or when not to use it.

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