karea_create_resource

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

No annotations are provided, so the description must fully disclose behavior. It states the tool creates and returns a resource with an ID, but omits details on side effects, permissions, overwrite behavior, or rate limits. For a creation tool, this is minimal 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 two sentences long, front-loaded with the core purpose, and contains no extraneous words. Every sentence earns its place.

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?

The description is adequate for a simple creation tool with 4 parameters and no output schema. It explains the action and return value (with ID), but lacks details on parameter interaction (e.g., required vs optional for folder/projectId) and the exact structure of the returned resource. Given the tool's complexity, it is minimally complete.

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 coverage is 100% with descriptions for all parameters. The description adds value by clarifying that the resource is a text resource and that creation occurs in a project or folder, mapping to the 'folder' and 'projectId' parameters. However, it does not elaborate on required params beyond the schema, so it adds moderate meaning.

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 verb 'create' and the specific resource type 'text resource (a note or document)', and mentions the location 'in a project or folder'. It also distinguishes from sibling 'karea_link_resource_to_task' by directing to that tool for attaching.

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 explicitly provides an alternative tool for attaching existing resources, which guides appropriate use. However, it does not mention when to use this tool over other creation tools like karea_create_task or prerequisites like needing a project, but the context is reasonably clear.

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