update_folder

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

With no annotations, the description must disclose behavioral traits. It does not mention idempotency, error handling, permission requirements, or effects of updating fields. The existence of an output schema is not leveraged to explain return behavior.

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 only 5 words, which is too short to convey essential information. While not verbose, it under-specifies the tool. It is not effectively front-loaded with key details.

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 complexity of 3 parameters (1 required) and no schema descriptions, the description is severely incomplete. It fails to explain which fields can be updated, constraints (e.g., folder_id format), or the output. The output schema is not referenced.

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 schema has 3 parameters with 0% description coverage. The description adds no meaning for any parameter: it does not explain that 'name' and 'fields_json' are optional or their purpose. The agent receives no help beyond the schema property names.

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 'Update a document folder' clearly states the action (update) and resource (document folder). It distinguishes the tool from create, delete, get, and list folder tools. However, it does not specify what aspects of the folder can be updated, which slightly reduces clarity.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives like create_folder or delete_folder, nor does it mention any prerequisites or context for updating a folder.

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