ensure_notes_folder_exists

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool ensures folder existence and creates it if missing, which implies a mutation operation. However, it lacks details on permissions required, idempotency (safe to call repeatedly), error handling (e.g., if creation fails), or side effects. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise and front-loaded, consisting of two short sentences that directly state the purpose and action. Every word earns its place, with no redundancy or unnecessary details. The structure is clear: first sentence defines the goal, second explains the mechanism.

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 low complexity (0 parameters, simple mutation) and the presence of an output schema (which likely covers return values), the description is minimally adequate. However, it lacks context on authentication needs, error cases, or integration with sibling tools (e.g., should this be called before 'create_note'?). With no annotations and a mutation operation, more completeness would be beneficial for safe usage.

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 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate. It implicitly confirms no inputs are required by focusing solely on the folder path ('/Notes'), which aligns with the empty schema.

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's purpose: 'Ensure that the /Notes folder exists in Nextcloud. Creates it if it doesn't exist.' This specifies the verb ('ensure exists'), resource ('/Notes folder in Nextcloud'), and action ('creates if missing'). It distinguishes from siblings like 'create_category' or 'create_note' by focusing on folder existence rather than content creation. However, it doesn't explicitly differentiate from potential folder-creation tools that might exist elsewhere.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication status), context for calling it (e.g., before note operations), or exclusions (e.g., when folder already exists). Sibling tools like 'check_webdav_login' might relate to setup, but no explicit comparison is made.

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