ghl_media_create_folder

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds no behavioral details beyond 'creates a new folder', such as side effects, idempotency, error conditions (e.g., duplicate name), or permission requirements. For a creation tool with openWorldHint=true, more transparency is needed.

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—three short sentences. The first line 'Create Folder' is somewhat redundant with the action statement. The endpoint detail, while possibly useful, is extra. Still, it is efficient and front-loaded with the purpose.

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 tool has no output schema, but the description does not mention what the response contains (likely the created folder object). It also fails to contextualize required parameters like altId (location) or parentId. For a creation tool, users would benefit from knowing the return value or typical behavior. The description is too sparse for full context.

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%: all parameters have clear descriptions (e.g., 'Name of the folder', 'Location Id', 'Type of entity (location only)', 'ID of the parent folder (optional)'). The tool description adds no additional parameter information beyond what the schema already provides. Baseline score of 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 clearly 'Creates a new folder in the media storage', specifying the verb 'creates' and the resource 'folder in media storage'. This distinguishes it from sibling media tools (e.g., upload, delete, list) which operate on files rather than folders.

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?

No explicit guidance on when to use or avoid this tool is given. The description does not mention alternatives or conditions. However, the tool name and purpose are clear enough that an AI agent can infer its usage in the context of media folder creation. The lack of explicit guidelines keeps it at a 'implied usage' level.

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