wealthbox.tasks.update

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'raw body' as an option, but does not explain whether updates are partial or full replacements, require an existing task, or what side effects occur. This lacks essential mutation transparency.

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 very short and front-loaded with the core action. The second sentence about raw body is somewhat vague and may not be essential, but overall the text is efficient and avoids unnecessary verbosity.

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?

With 8 parameters, no parameter descriptions, no annotations, and no output schema, this description is too thin to guide an agent reliably. It lacks update semantics, parameter constraints, and return-value expectations, making it a minimal placeholder rather than a complete tool definition.

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 0%, yet the description only explains 'id' and hints at 'raw body' (corresponding to the 'body' property). The other six parameters (title, due_date, category_id, description, assigned_to_team_id, assigned_to_user_id) have no semantics provided, and 'raw body' is vague about format or precedence.

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 task') and the required identifier ('by id'), which distinguishes it from sibling tools like create, get, delete, and list. The additional note about raw body hints at advanced usage but doesn't obscure the core purpose.

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 description implies usage for modifying an existing task via its id, giving a clear general context. However, it provides no explicit guidance on when to use this tool versus alternatives (e.g., create or delete) and no exclusions or caveats.

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