Ensure the current user's personal skill folder exists

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

The description states 'ensure' implying idempotent creation, but annotations set idempotentHint=false, creating a contradiction. Beyond the title and auth class, no additional behavioral traits (e.g., what happens if folder exists, side effects) are disclosed. The annotations already provide some info, but the description adds confusion.

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 the first sentence redundantly repeats the title. It lacks structure and leaves out critical information, making it under-specified rather than concise.

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?

With two parameters (including nested objects), an output schema, and sibling tools, the description is severely incomplete. It does not explain the return value, the 'ensure' semantics, or the meaning of the slug. The agent has insufficient context to use the tool correctly.

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%, yet the description provides no explanation of the two required parameters (path.companyId and body.slug). The optional slug parameter's purpose and format are not described, leaving the agent with only the schema constraints.

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 title and first sentence clearly state the tool's purpose: ensuring the current user's personal skill folder exists. However, it does not differentiate from sibling folder tools like pc_post_companies_by_company_id_folders, which creates a folder. The term 'ensure' implies idempotent behavior but is not explicitly contrasted.

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 vs. alternatives (e.g., creating a folder). The description mentions authorization class but does not specify context, prerequisites, or exclusions.

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