Create a folder

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description adds authorization class ('board_or_agent') but does not disclose other behavioral traits like idempotency, error behavior, or side effects. The description provides minimal additional value beyond annotations.

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 very short (two sentences) but under-specifies important aspects. It is not concise in the sense of being informative; it is merely brief.

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 a complex input schema with nested objects and enums, but the description provides no context about what the tool returns, how to structure the body, or when to use optional fields. The existence of an output schema is noted but the description does not leverage it.

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 0%. The description does not explain any of the parameters (companyId, kind, name, slug, color, parentId, position) or their roles. The agent must rely solely on the schema, which lacks semantic context.

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 'Create a folder' which matches the title, but it does not differentiate from sibling tools like 'pc_post_companies_by_company_id_folders_ensure_my' which also creates a folder. The HTTP path and authorization are mentioned, but the specific purpose among similar folder creation tools is unclear.

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 guidance on when to use this tool versus alternatives such as 'ensure_my' or 'patch' or 'delete' folder tools. The description lacks any contextual cues for selection.

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