Coda Create Folder

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the mutating nature is covered. The description adds useful output context ('Returns the new folder's ID and metadata') in the absence of an output schema, but discloses nothing about permissions, workspace requirements, or failure modes.

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 opening two sentences are largely redundant — 'Create a new folder in a Coda workspace' and 'Creates a folder in the specified workspace' restate the same fact. The return-value and usage notes earn their place, but the overlap wastes space and blurs the front-loading.

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?

For a simple, fully-documented create tool, the description covers purpose, the returned value, and a follow-up usage path, which is enough to invoke it correctly. Missing only edge-case behavior (naming conflicts, permission requirements), which is minor at this complexity level.

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 100%, so the schema fully documents name, description, and workspace_id. The description adds no syntax, format, or constraint details beyond what the schema already provides, so the baseline 3 is appropriate.

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 states a specific verb and resource ('Create a new folder in a Coda workspace') that clearly distinguishes it from the list/get/update/delete folder siblings. It also names coda_create_doc as the downstream consumer of the returned folder ID. It stops short of explicitly contrasting its scope against siblings beyond that link.

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?

It gives workflow context ('Use the folder ID when creating docs with coda_create_doc to organize them'), which implies when the tool fits into a broader flow. However, it offers no explicit when-to-use/when-not guidance, prerequisites, or comparison to alternatives like update_folder or delete_folder.

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