output_folder

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

With no annotations, the description must carry the full behavioral burden, but it does not say whether invoking the tool has side effects, whether it is read-only, or what kind of value it returns. The output schema exists, so return format need not be explained, but basic behavior remains undisclosed.

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 definition is a single short sentence with a useful parenthetical, so it is appropriately sized and front-loaded. It is concise, though the fragmentary wording leaves the core action implicit.

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 zero parameters and an output schema, the description need not explain return values, but it still fails to say what calling the tool does. For an agent choosing among notebook and page tools, the definition is too thin to be reliably actionable.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and nothing in the schema coverage creates a gap.

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 says what the folder is for ('Where written notebooks go') and adds an import hint, but it never states the action the tool performs, such as returning the output folder path. An agent can infer it relates to output location, but the purpose is vague rather than a specific verb+resource.

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?

There is no explicit guidance on when to use this tool versus siblings like list_notebooks or export_pdf. The parenthetical 'import them in Noteful via Files' hints at a workflow but does not say when the agent should call this tool.

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