Update Folder

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

No annotations are provided, so the description must carry the behavioral load. It discloses only the mutation itself; it does not mention write side effects, required permissions, optimistic concurrency via fingerprint, or effects on child entities. This leaves the agent to infer behavior from the tool name.

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?

Single sentence, front-loaded, and free of filler. It is efficient, but so brief that behavioral and usage context must be pulled from elsewhere, preventing a top score.

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 the complete parameter schema and the presence of an output schema, the description is minimally adequate for constructing a call. However, it leaves out usage alternatives and behavioral side effects, so it is not fully complete for an unannotated mutation tool.

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?

All parameters have schema descriptions, but the nested `folder` object is defined only as 'the fields to set' with additionalProperties allowed. The description adds value by identifying 'name or notes' as the relevant settable fields, which the schema alone does not specify.

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 an explicit verb ('Update'), resource ('folder'), and target fields ('name or notes'), making its role clear. It distinguishes from create/get/delete/revert folder tools by operation and target, though it does not name an alternative explicitly.

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 about when to choose this over create_folder, delete_folder, revert_folder, or move_entities_to_folder, and no prerequisites such as an existing folder or required permissions are mentioned. The only usage signal is the verb 'Update,' which is insufficient.

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