coda_create_folder

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

The annotations indicate this is a mutation (readOnlyHint=false) and may have side effects (openWorldHint=true). The description adds that it returns ID and metadata, but does not disclose any additional behavioral traits like permission requirements or rate limits.

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 concise with two sentences, front-loaded with the purpose and followed by a useful usage hint. No unnecessary words.

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 tool's simplicity and the presence of an output schema, the description adequately explains the action and how to use the result. The mention of workspace and folder ID provides sufficient context for an agent.

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% coverage, so the description does not need to add detail. It does not elaborate on the parameters beyond what the schema provides, warranting a baseline score of 3.

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 tool creates a new folder in a workspace, specifies that it returns ID and metadata, and differentiates from other tools like coda_create_doc and coda_update_folder.

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 provides usage context by suggesting to use the returned folder ID with coda_create_doc for organization. However, it does not discuss when not to use this tool or mention alternatives like coda_update_folder.

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